Release Asuswrt-Merlin 3004.388.8_2 is now available

[Kees17760]

Big Thanks to

RMerlin​

for all the good work and thinking along!

 

[Cluelessin2023]

Thanks @RMerlin.

Just upgraded to 3004.388.8_2 and the "firmware check button" is back on my RT AX3000 and everything works well.

​

 

[Aiadi]

Thanks again to Merlin for the rapid update. Interesting to know why GT-AX6000_3004_388.8_2 download size is more than double the size of GT-AX6000_3004_388.8_0 (which is also less than half the size of the few versions prior). I have found GT-AX6000_3004_388.8_0 to be quite buggy with loss of internet on connection to Wireguard client until reboot and with my problem with rogue DHCP behaviour. that I have encountered for the first time ever with that version. Will see how it goes with this new version.

 

[octopus]

Just updated my GT-AX6000 and working fine.

When you press apply in wireguard client 2 after you have configured something,
"vpnclient2-up" and "vpnclient2-route-pre-down" are triggered which it should not be.

Thank you for new software.

 

[elbubi]

Interesting to know why GT-AX6000_3004_388.8_2 download size is more than double the size of GT-AX6000_3004_388.8_0 (which is also less than half the size of the few versions prior).

Thats because 388.8_0 lacked rog_nand version, which 388.8_2 does not.

 

[Funnyland123]

Hello everyone, I also put 3004.388.8_2 on it. I have attached a 1 minute syslog. AX86U

Could someone explain to me what that means??

Because this is shown so often:

Deauth_ind 1C:90:FF:E7:37:C6

 

[zer0bitz]

Hello everyone, I also put 3004.388.8_2 on it. I have attached a 1 minute syslog. AX86U

Could someone explain to me what that means??

Because this is shown so often:

Deauth_ind 1C:90:FF:E7:37:C6

Some device is being disconnected from the wireless network.

 

[kda]

update 3004.388.8.2 installed today at 01-08-2024 on a AX-RT-88U, a vonets adapter on 5G didn't work, lost connection when i update the routers on this last release.
there was not a problem on the alpha and the beta release
i have found this link: https://www.asus.com/support/faq/1042475/
when i have changed this on the 5 Gig, there was the connection again.
This problem wasn't on the alpha and the beta release from 3004.388.8.2 only on the final release.
The vonets (VAP11AC) is on the last update (3.3.24.7.26 ( Jul 26 2024 11:17:41 ))

 

[Funnyland123]

Some device is being disconnected from the wireless network.

OK

But that happens every 1 or 2 seconds, is that normal?

 

[eibgrad]

OK

But that happens every 1 or 2 seconds, is that normal?

Have you tried rebooting the device w/ that MAC address?

 

[Ripshod]

Sanity check please. Since moving from 388.8 to 388.8_2 I can't contact my server remotely. I've checked IPs on my local network and everything is fine there, which leads me to believe port forwarding is broken. Is it just me?

Yes, insanity strikes again. I'd connected my server to an external vpn last night for a test.

 

[Funnyland123]

Have you tried rebooting the device w/ that MAC address?

I just did the entire house without electricity and restarted everything. Unfortunately that didn't help

 

[eibgrad]

Sanity check please. Since moving from 388.8 to 388.8_2 I can't contact my server remotely. I've checked IPs on my local network and everything is fine there, which leads me to believe port forwarding is broken. Is it just me?

If we're talking about plain ol' ordinary port forwarding (not involving VPNs), then no, I've seen no such reports. If you have such a problem, I strongly suggest starting a new thread, because I can imagine this quickly turning into a need for internal dumps and a lot of back and forth.

And if you do, then perhaps cut to the chase and dump everything.

ifconfig
brctl show
ip route
ip rule
iptables -vnL
iptables -t nat -vnL

Feel free to mask your public IP. Just make it obvious and consistent.

 

[Ripshod]

Forget my last post. I had my server routed to an external vpn. No wonder I couldn't connect to it.

 

[MDM]

I just did the entire house without electricity and restarted everything. Unfortunately that didn't help

Dont tell me you dont know which exact device is causing this?
You cannot fix this, if you first dont know that...

 

[Funnyland123]

Dont tell me you dont know which exact device is causing this?
You cannot fix this, if you first dont know that...

Exactly no idea which device is causing it.

I'm still looking.

I disabled Wifi 2.4 once. Still.

Then guest network.
Still.

Then turned 2.4ghz and guest network back on and 5ghz off. Then it was gone.

So I think it's a device that uses 5 GHz.

To test, turned 5 GHz back on on the router. The problem hasn't come back yet. I don't really understand because I have maybe 5 - 6 devices running at 5ghz and none of them have the Mac address.

It can't be a neighbor - I don't have one.

 

[ColinTaylor]

Exactly no idea which device is causing it.

I'm still looking.

I disabled Wifi 2.4 once. Still.

Then guest network.
Still.

Then turned 2.4ghz and guest network back on and 5ghz off. Then it was gone.

So I think it's a device that uses 5 GHz.

To test, turned 5 GHz back on on the router. The problem hasn't come back yet. I don't really understand because I have maybe 5 - 6 devices running at 5ghz and none of them have the Mac address.

It can't be a neighbor - I don't have one.

It's an IoT device (Tuya) that's bouncing between the normal 2.4GHz SSID and the 2.4GHZ guest SSID.

 

[Funnyland123]

Are you sure ?

2.4ghz and guest network have absolutely different names.

Secondly: when I turn both off it was still there so I think it must be a 5ghz

 

[ColinTaylor]

2.4ghz and guest network have absolutely different names.

That's what the log file you posted showed.

Do you have 802.11ax / WiFi 6 mode enabled for the 2.4GHz band? If so disable that (assuming none of your 2.4GHz clients use ax) and see if the messages disappear.

EDIT: If you have WPA3 enabled for that band try changing it to WPA2-Personal only.

Secondly: when I turn both off it was still there so I think it must be a 5ghz

Post the new log file that shows that.

 

[kuchkovsky]

I’m getting an error when running a Time Machine backup on the 3004_388.8_2 firmware. I’m not sure if this is related to the latest update, but the previous backup yesterday was successful. Also, I verified the sparse bundle, and it’s not corrupted.

Aug  1 16:55:02 afpd[25490]: AFP3.3 Login by kuchkovsky
Aug  1 16:55:02 afpd[25490]: get_tm_bandsize("/tmp/mnt/sda1/._MacBook Pro.sparsebundle/Info.plist"): Not a directory
Aug  1 16:56:06 afpd[25490]: get_tm_bandsize("/tmp/mnt/sda1/._MacBook Pro.sparsebundle/Info.plist"): Not a directory
Aug  1 16:56:06 kernel: potentially unexpected fatal signal 6.
Aug  1 16:56:06 kernel: CPU: 2 PID: 25490 Comm: afpd Tainted: P           O      4.19.183 #1
Aug  1 16:56:06 kernel: Hardware name: RTAX88U_PRO_HWB (DT)
Aug  1 16:56:06 kernel: pstate: 000f0010 (nzcv q A32 LE aif)
Aug  1 16:56:06 kernel: pc : 00000000f79503a4
Aug  1 16:56:06 kernel: lr : 00000000ffeabaa8
Aug  1 16:56:06 kernel: sp : 00000000ffeabaa8
Aug  1 16:56:06 kernel: x12: 0000000000000000
Aug  1 16:56:06 kernel: x11: 00000000ffeabd38 x10: 00000000f7a46e10
Aug  1 16:56:06 kernel: x9 : 0000000000000002 x8 : 0000000000000001
Aug  1 16:56:06 kernel: x7 : 00000000000000af x6 : 00000000ffeabce8
Aug  1 16:56:06 kernel: x5 : 00000000ffeabce8 x4 : 0000000000000006
Aug  1 16:56:06 kernel: x3 : 0000000000000008 x2 : 0000000000000000
Aug  1 16:56:06 kernel: x1 : 00000000ffeabaa8 x0 : 0000000000000000