Release Asuswrt-Merlin 3004.388.8_2 is now available

[bmwjavier]

RMerlin obviously meant flushing the browser cache, with CTRL-F5...

Also dont take it wrong, but if you dont yet know something that basic; flashing a modified FW to your router might have no point for you and even be dangerous (bricking it or just misconfiguring it etc.)?

RMerlin said: "If you have just gone from ROG to regular UI, I recommend flushing the cache as a few cached files (mostly CSS and JS) will be different." I'm sorry, but it didn't seem obvious to me that it was referring to the browser's cache. I have Merlin in my last 3 Asus routers and I also have a FRITZ!Box 7520 with openwrt. I don't have any problem flashing a modified FW. Thank you.

 

[pirx73]

- REMOVED: Wifi Radar was removed (unsupported by Wifi 7 devices, and security issues cited by Asus in their own recent releases).

This made me a sad panda

 

[eibgrad]

Hi guys,

Comparing (very raw) the 2 logs from both 7 and 8 firmware, is there any hint on this ?

View attachment 60477

On the left is the latest one, on the right is the one actually working.

Thanks !

vpn problems in asuswrt merlin 3004.388.8

Hi, I have the following setup up and running and it is working like a charm OpnSense RT-AX58U 3004.388.7 (asuswrt merlin) OpnSense (iPhone/Mac) I can connect from the OpenVPN Roadwarrior to like everything. Today I tried to replicate that for a friend and it didn't work. OpnSense...

www.snbforums.com

 

[underdose]

Dirty upgrade from beta and nothing to report. Thank you for the great release, Eric!

 

[iBest]

Can't believe i had also found the error in the logs

Thank you !

 

[GHammer]

Not necessarily. Some devices carry Windoze drivers and software on a partition that mounts as a cd-rom drive. That said, that is exactly what the problem is here.
@Rob90 I don't understand how you were ever able to use this dongle.

When I had such 'helpful' driver partitions, I deleted he partition using GParted.
Don't dink with anything else.
YMMV

 

[monakh]

Anything that's routed through a VPN client will be subject to the killswitch. Anything that is routed through the WAN won't be. So if you add a rule that routes the router's IP through the WAN, it won't be affected.

A killswitch cannot be selective. If a client is tied to a VPN, then that client is subject to the killswitch if it's enabled.

@RMerlin, is this true even if the client is disabled? I have tried adding the router IP through the WAN but it's still not letting any traffic through when the VPN client is not enabled. What's the trick here? Am I missing something?

Did a dirty upgrade from 7 to 8 and everything is fine and the traffic block is probably due to the change log, I guess, I'll figure it out sooner or later.

Edit: Never mind, I forgot the /24 next to the router IP and that fixed it. Note to all, if you have a VPN client setup and even if it is not in use WITH the killswitch option, your traffic will be blocked after this upgrade by default. To fix this, just create a rule like this for the WAN interface under VPN Director:

Local IP
Your Router IP/24

You can leave the Remote IP field blank. That should do it.

 

[Mutzli]

Updated 2-1/2 days ago from beta and everything works as expected. Wireguard VPN is working well too.

 

[Zork]

Just dirty update on AX6000 and aimesh node ax86U, both working as normally

 

[fka]

Don't redirect the entire subnet. Exclude the router's own IP from it.

Anything that's routed through a VPN client will be subject to the killswitch. Anything that is routed through the WAN won't be. So if you add a rule that routes the router's IP through the WAN, it won't be affected.

A killswitch cannot be selective. If a client is tied to a VPN, then that client is subject to the killswitch if it's enabled.

Many thanks Merlin!

 

[RMerlin]

Does this dongle include an sdcard slot? Is there anything in it?

Some of these devices will "boot" into Mass Storage mode, to expose a virtual CD containing the driver. Asuswrt has a script that will switch it into a network device mode.

I've never looked at that portion of the code because I have no way to test anything there, so I'm not familiar at all as to how it works - that code was kept unchanged from upstream. If the dongle appears as a mass storage device, someone should dig through the modem handling code to retrieve the method to switch it into modem mode.

 

[RMerlin]

@RMerlin, is this true even if the client is disabled?

Yes.

 

[pirx73]

@RMerlin WiFi Radar gone forever? Nothing coming in from Asus to replace it in the future?

 

[RMerlin]

Nothing coming in from Asus to replace it in the future?

No. Wifi Radar was based on Broadcom's Visualizer, an example application from their SDK. They never updated it over the years, so Asus chose to stop using it, both because it was partly broken (didn't support WIfi 6e or 7 as Broadcom never updated it), and because of inherent security issues since the code was unmaintained.

 

[Deetlemore]

Happy to report that this update fixed my weird DDNS issue. The forced WAN IP verification used to work very intermittently despite being set to check once an hour and would get stuck in a "verification loop" whenever my WAN connection went down. I haven't had any issues since updating.

 

[lgkahn]

n (didn't support WIfi 6e or 7 as Broadcom never updated it), and because of inherent security issues since the code was unmaintained.

ya what a waste it is going to be years before i have wifi 7 client .. i only have two wifi 6 clients.. and the range is not overly impressive.

 

[maxbraketorque]

Switched from 388.7 to 388.8 on my GT-AX6000 main/AP combo a few days ago. No issues so far. I see some discussion in this thread of OVPN issues, but I'm not seeing any with my site-to-site OVPN link to an RT-AX86U Pro running 388.8a1.

 

[Karmatron]

Dirty update from Asuswrt-Merlin 3004.388.7 on my RT-AX86U went well as far as I can tell, but for one small issue. OpenVPN client can't detect the public IP anymore.

 

[kuposcar]

Thank you for including RT-AX56U

 

[Catalinus]

On my AX88U I tried a dirty upgrade from 388.7 to 388.8 and that has placed things in a very bad configuration from where no kind of network (wireless or wired) was working. Since unfortunately for the next two weeks or so I can't investigate further on that router what is wrong I had to factory reset, return to 388.7 and restore JFFS/configuration.