Really never knew that always thought to have all merlin rather than mix. ThanksYou are better off running Asus firmware on the nodes
Really never knew that always thought to have all merlin rather than mix. ThanksYou are better off running Asus firmware on the nodes
AiMesh settings synchronization service, outside of my control.Something is not right with this beta2 on my AX86S:
What do you have in the port forwarding? Is UPNP enabled?Anyone knows of reason why my Plex remote access has stopped working with this beta version installed and with full factory reset and with all the setting exactly as they were with the previous stable version of the firmware on my GT-AX6000? My Plex server is excluded from wireguard VPN client use as always using VPN director and plex server is getting public IP from ISP as expected and with port forwarding set up correctly pointing to my Plex server as usual.
Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):What do you have in the port forwarding? Is UPNP enabled?
View attachment 52274
Do you have "WAN IP and hostname verification" enabled on the DDNS settings page?I don't know if it is the same thing but I posted below few pages back.
"I disconnected manually my PPPoE connection earlier to get a new IP address from the GUI (Network Map-> Internet Connection) but ddns-start script did not kick in."
Above still exists in beta-2.
I know this doesn't help you (sorry) but I have an AX86S and it is working great with beta 2. For me the most stable 388.x by far.Something is not right with this beta2 on my AX86S:
After some time/days I see this in syslog:
Code:Aug 10 16:25:56 kernel: CPU: 0 PID: 2691 Comm: cfg_server Tainted: P O 4.1.52 #2 Aug 10 16:25:56 kernel: Hardware name: Broadcom-v8A (DT) Aug 10 16:25:56 kernel: task: ffffffc001f4b580 ti: ffffffc011b50000 task.ti: ffffffc011b50000 Aug 10 16:25:56 kernel: PC is at 0x2a7bc Aug 10 16:25:56 kernel: LR is at 0x2a78c Aug 10 16:25:56 kernel: pc : [<000000000002a7bc>] lr : [<000000000002a78c>] pstate: 80010010 Aug 10 16:25:56 kernel: sp : 00000000f6749bf8 Aug 10 16:25:56 kernel: x12: 00000000000be190 Aug 10 16:25:56 kernel: x11: 00000000f65194e0 x10: 00000000f651b270 Aug 10 16:25:56 kernel: x9 : 00000000f6749c84 x8 : 00000000ffdba032 Aug 10 16:25:56 kernel: x7 : 000000000000000c x6 : 00000000f6ff0ab8 Aug 10 16:25:56 kernel: x5 : 00000000f6517290 x4 : 00000000f65130c8 Aug 10 16:25:56 kernel: x3 : 00000000000a5180 x2 : 00000000f6500470 Aug 10 16:25:56 kernel: x1 : 000000000000001d x0 : 0000000000000000
You are doing manual port forwarding so upnp is not required. Why would you need 2 port forwards - just use one and select 'both' in the protocol selector?Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):View attachment 52276
Do you have "WAN IP and hostname verification" enabled on the DDNS settings page?
In 23588, Asus seems to rely on the watchdog checking at regular intervals rather than automatically re-running the client at reconnection time. I need to check with them the reason behind this change before reverting it.
Plex isn't working for me without upnp. In their documentation they specify one port, but if you forward just that port, I cannot access server outside of network.Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):View attachment 52276
They do use also port 443, but that is initated from within your local Plex server and doesn't need a forwarding rule in your router.Plex isn't working for me without upnp. In their documentation they specify one port, but if you forward just that port, I cannot access server outside of network.
Only when I enable upnp access start working. So, they probably need more then one port, just not sure which, and I'm not willing to keep upnp ON.
Sorry to post about this here again but I am pretty confident that this is a firmware problem as my settings (below) have not changed one bit from my previous ones (and I try to keen things as close to default as possible) and I have only been unable to get Plex remote access with this version of AsusMerlin and with no other changes to my plex server either. Why has it stopped working as soon as I upgraded to this beta?
View attachment 52287View attachment 52288View attachment 52289
Honestly, as I said before the only variable here is moving from GT-AX6000_388.2_2_stable to GT-AX6000_3004_388.4_beta2. I guess that I will just have to revert back to the latest stable.Any chance your getting CGNAT/ Double Nat IP from Your ISP?
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!