What's new

[ 3004_388.8_3 Build(s) ] available build(s)

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

So far all things working great on:
AX88U Pro
AX86U
AX58U
 
Works fine as always.

But did not have THE issue anyway, because I would newer dream of enabling AiCloud (or any WAN aces) except VPN in the first place... ;)
 

3004.388.8_4 (xx-xxx-2024)
- CHANGED: VPN killswitch will now only be active if the
VPN client itself is enabled. If you stop/start
the client yourself over SSH, you need to also
update the enabled/disabled nvram setting.
- FIXED: Security issues in AiCloud (backports from Asus)
- FIXED: CVE-2024-2511, CVE-2024-4741, CVE-2024-5535 &
Implicit rejection for RSA PKCS#1 in openssl
(backport from Ubuntu by RSDNTWK)
Works fine on AXE1600 & Ax88. Thanks!
 
Smooth update on primary router...
 
Rebooted my RT-AX88U router this morning and none of my 5GHz devices could connect. Didn't want to rebuild everything for an alpha and risk this happening again, so I'm back on 388.8_2 - for now.
 
Rebooted my RT-AX88U router this morning and none of my 5GHz devices could connect. Didn't want to rebuild everything for an alpha and risk this happening again, so I'm back on 388.8_2 - for now.

Odd, I would have tried flashing the _3 a second time on top.
 
Odd, I would have tried flashing the _3 a second time on top.
Thanks. You made me look at this again and it appears Link Aggregation to my switch was disabled somehow, causing dhcp problems. Gonna fire up this alpha again, check LACP and run another long term test.
 
Updated after 106 days of uptime, no issues so far on any of my routers.
 
Ok, calling @eibgrad: How do we now reimpose the former killswitch behavior? I do not want two devices ever to connect to the internet except over the tunnel designated in VPN Director. :) Even if the tunnel is down.

The kill switch implementation has changed so many times, it's NOT even consistently implemented across the 386 and 388 builds. So trying to keep track of it anymore is a lesson in frustration.

All I can recommend is using my firewall script, which I wrote quite some time ago to sidestep the built-in kill switch (whatever its current implementation).


Note: I haven't touched it in ages, so I can't say w/ 100% certainty it still works (I assume so since no one has reported otherwise).
 
Seems like I'm blind, but I don't see RT-AX86U PRO, 3004_388.8_4
Per RMerlin on page 1:
Odd revision number = beta, even revision number = final release.
RT-AX86U_PRO_3004_388.8_3-g9b85de2f5e.zip is the correct Test Build file to download for the RT-AX86U Pro.
 
Seems like I'm blind, but I don't see RT-AX86U PRO, 3004_388.8_4
An error on the post by octopus. It is not 3004.388.8_4 (xx-xxx-2024)... It is 3004.388.8_3...
 
Nothing to report over here. Working smooth and steady.
 
Thanks for this new update.
Is it necessary to reset the router after this new update or is it considered minor ?
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top