Beta Asuswrt-Merlin 3004.388.4 beta is now available

[garysteel]

You are better off running Asus firmware on the nodes

Really never knew that always thought to have all merlin rather than mix. Thanks

 

[RMerlin]

Something is not right with this beta2 on my AX86S:

AiMesh settings synchronization service, outside of my control.

 

[Clark Griswald]

RMerlin has enough work, and I'm glad there are things out of his control.
Both RMerlin FWs working well in my environment!

 

[rwheaton1]

@RMerlin What log files do you need to see if everything is working? I have a ROG GT-AX11000 Pro backhauled to a ZenWiFi Pro XT12. Don't know if my messages file helps out any...attached. It has some info. from May 5th...probably when I upgraded.

 

[Aiadi]

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.

 

[vlord]

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.

What do you have in the port forwarding? Is UPNP enabled?

 

[Aiadi]

What do you have in the port forwarding? Is UPNP enabled?
View attachment 52274

Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):

 

[SuperFreaky]

Gave this firmware another shot, did all the reset measures that @L&LD recommends and everything is fine again.

 

[Mutzli]

It's running now for more than 5 days without any issues on all of my routers:

I haven't done a router reset for a year now. I'm just making sure to clear the cache to free up all the RAM before I do an update and after the update wait about 10 minutes before I do a manual restart.

 

[RMerlin]

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.

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.

 

[jata]

Something is not right with this beta2 on my AX86S:
After some time/days I see this in syslog:

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

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.

 

[jata]

Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):View attachment 52276

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?

Have you checked your plex settings to see if they are correct/aligned with your manual port forwards?

I stopped using manual redirect for plex years ago as it all works great using upnp from any deviice without any client side config (just your plex login).

Maybe try using upnp to see if you can get it working with plex?

 

[spykos]

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.

WAN IP and hostname verification was always set to no. Note that this option does not exist if someone is using www.asus.com or custom.

 

[Mikeyy]

Thanks my settings are (and yes, upnp is on but that shouldn't really matter, should it?):View attachment 52276

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.

 

[FlamingIce]

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.

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.
I have just set port 32400 fixed in Plex and in my Asus and it is working perfectly. Have also a look at your firewall rules at your Plex server itself.

 

[Interfreak]

Still very stable on my AX86U Pro, looking forward to beta 3 and the eventual full release.

@RMerlin - thank you very much for your continued hard work.

 

[Aiadi]

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?

 

[Damit1]

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

Any chance your getting CGNAT/ Double Nat IP from Your ISP?

 

[Damit1]

Waiting for B3, hopefully still this weekend.

 

[Aiadi]

Any chance your getting CGNAT/ Double Nat IP from Your ISP?

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.