Release Asuswrt-Merlin 3004.388.4 is now available

[Tech9]

Except that I mentioned it also happened with stock 388 release of ASUSWRT

I don't see similar issues mentioned in Asuswrt firmware release threads. Must be something on your network.

 

[aex.perez]

or uou may have forgotton - https://www.snbforums.com/threads/skynet-dnsmasq-flowcache-merlin-388-releases.85330/#post-846732

 

[Tech9]

This is your thread again, no? Follow this advice:

Skynet / dnsmasq / Flowcache / Merlin 388 releases

No one knows. As per this post there is something else used. This is not that important. What is important very often what I find issues with in 388 firmware works well in later 386 firmware. In my understanding and experience so far firmware version below 38x.4xxxx -> user as a beta tester.

www.snbforums.com

 

[JGodfrey82]

Since upgrading my AX-86U to this firmware my secondary wan connection using a USB modem keeps going offline saying the dhcp server isn't functioning properly. I never had this issue on past firmwares and wan1 would stay connected as backup connection for weeks without any issue. What should I do to troubleshoot this?

Just FYI I think I found a resolution to this issue, this only started on the 388 version firmware but anyone having an issue keeping a usb modem online may want to try this. I set the MTU to 1428 and also set the extend TTL value for the modem to yes.

 

[Damit1]

27 days.
Oh man, that's sweet.

One bug I noticed- @RMerlin FYI.

If I DISABLE WAN (in order to redial on PPPoE and re gain new IP address), SSL does not auto renew itself, or something likw that.

Had to do it twice, and you get SSL error.
I have to cancel DDNS, then the SSL.
Apply, re enable them.
How do I know it does not auto renew?

I enter the app, it would usually not let me inside the network from Remote, Then show Security Link

That's all for today.

 

[John35]

There's 29 pages in the thread, so apologies if I'm missing anything relevant, but I have this issue where my Asus RP-AC68U, which I'm using as a Media Bridge to provide high-speed Ethernet (well, 1Gb/s anyway) to a bunch of upstairs devices, has all these errors (in the GT-AX6000's log) with the 2.4GHz connection (way way more than shown here). So I wonder if anyone has any ideas of stuff to check/tweak? I did check and no neighbours have anything interfering with the channel...

The entire log window is full of these, starting at:

Sep 26 23:37:57 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:0
Sep 26 23:37:57 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:0
Sep 26 23:38:02 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 26 23:38:02 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 26 23:38:02 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-69
Sep 26 23:38:02 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-69
and ending at:
Sep 27 00:09:33 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:0
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-71
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Unspecified reason (1), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(685): eth6: Auth D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:09:38 wlceventd: wlceventd_proc_event(722): eth6: Assoc D0:17:C2:C7:A3:E8, status: Successful (0), rssi:-70
Sep 27 00:10:42 wlceventd: wlceventd_proc_event(645): eth7: Deauth_ind D0:17:C2:C7:A3:EC, status: 0, reason: Disassociated due to inactivity (4), rssi:-67
Sep 27 00:10:43 wlceventd: wlceventd_proc_event(645): eth6: Deauth_ind D0:17:C2:C7:A3:E8, status: 0, reason: Disassociated due to inactivity (4), rssi:-71


Notes:
I turned it off at the end of the log, the log had no additional entries by this morning, until I turned the bridge on again. (I also have a EA-AC87 bridge which is working fine.)

D0:17:C2:C7:A3:E8 is 2.4GHz

D0:17:C2:C7:A3:EC is 5GHz

D0:17:C2 -> ASUSTek COMPUTER INC.

There are very limited configuration options on the RP-AC68U when in media bridge mode, I don't think I can even disable the 2.4GHz (I could perhaps nuke the ssid), so changes would have to be at the GT-AX6000 end.

P.S. The RP-AC68U's log says:

Sep 27 11:23:16 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:23:16 kernel: wl0: Open and authenticated
Sep 27 11:23:34 kernel: wl0: Roaming...
Sep 27 11:23:35 kernel: IQ Calibrate
Sep 27 11:23:35 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:23:35 kernel: wl0: Open and authenticated
Sep 27 11:23:51 kernel: wl0: Roaming...
Sep 27 11:23:52 kernel: IQ Calibrate
Sep 27 11:23:52 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:23:53 kernel: wl0: Open and authenticated
Sep 27 11:24:16 kernel: wl0: Roaming...
Sep 27 11:24:17 kernel: IQ Calibrate
Sep 27 11:24:22 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:24:25 kernel: wl0: Open and authenticated
Sep 27 11:24:40 kernel: wl0: Roaming...
Sep 27 11:24:41 kernel: IQ Calibrate
Sep 27 11:24:41 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:24:42 kernel: wl0: Open and authenticated
Sep 27 11:24:49 kernel: wl0: Roaming...
Sep 27 11:24:50 kernel: IQ Calibrate
Sep 27 11:24:50 kernel: wl0: WPA-none PSK authentication in progress...
Sep 27 11:24:50 kernel: wl0: Open and authenticated

 

[ColinTaylor]

@John35 Do you have Roaming assistant enabled in the Wireless - Professional settings? Your devices are disconnecting at about -70 dBm which is exactly the threshold set by Roaming assistant.

 

[John35]

@John35 Do you have Roaming assistant enabled in the Wireless - Professional settings? Your devices are disconnecting at about -70 dBm which is exactly the threshold set by Roaming assistant.

Great idea, thanks, but alas...

I did disable "Multi User MIMO", "Explicit Beamforming" and "Universal Beamforming" for 2.4GHz in case there's anything there that might help, but made no difference.

 

[L&LD]

@John35, that is not what your screenshots show.

After you have changed the settings, try also 'forgetting' the network on the problem device(s), rebooting/power cycling the device(s) and the router, and then re-associating them again.

After the reboot, before you re-associate anything, double-check that the settings are as you intend them to be.

 

[John35]

@John35, that is not what your screenshots show.

After you have changed the settings, try also 'forgetting' the network on the problem device(s), rebooting/power cycling the device(s) and the router, and then re-associating them again.

After the reboot, before you re-associate anything, double-check that the settings are as you intend them to be.

"that is not what your screenshots show." - sorry, Roaming Assistant shows as disabled doesn't it?
The disabling other things I did later...

 

[htismaqe]

I saw this reported in the 386.12 thread and I just had it now with 388.4.

Changes to hostnames aren't saved. In the 386.12 thread, somebody suggested re-flashing but I didn't have to go that far. One reboot and it was working again. We'll see if it comes back over time.

 

[John35]

Oh and if anyone has any suggestions on tweaking any of the settings in my "professional settings" images above i'd appreciate it. I find the GT-AX6000 radios to be significantly less good than my RT-AC87U's ones, which might be a firmware setting or something in the firmware, possibly?
For example I am getting 6Mbps to the 2.4GHz radio and 500-750Mbps to the 5GHz on the RP-AC68U now vs. 195/975 with the RT-AC87U (both in the same positions).

 

[John Fitzgerald]

Oh and if anyone has any suggestions on tweaking any of the settings in my "professional settings"

Turn off "Universal Beamforming " for both bands. The 5G is off and the 2.4G is on.

 

[John35]

Turn off "Universal Beamforming " for both bands. The 5G is off and the 2.4G is on.

Thank you, appreciated.

BTW as the 2.4GHz has gone from 195Mbps with the RT-AC87U to 6Mbps with the GT-AX6000 I've just disabled it at the Media Bridge since it's pointless. Pity the radios in the new router aren't better though... Oh and I reset the media bridge and completely set it up again from scratch, which made no difference (actually twice, the second time as you can't turn off the 2.4GHz later on). Alas the marginally more recent firmware I added (before my original post, it didn't change anything speed related) meant I could only administer it from the Ethernet side, which was a little annoying and sorted by a Pi4...

 

[John Fitzgerald]

Thank you, appreciated.

BTW as the 2.4GHz has gone from 195Mbps with the RT-AC87U to 6Mbps with the GT-AX6000 I've just disabled it at the Media Bridge since it's pointless. Pity the radios in the new router aren't better though... Oh and I reset the media bridge and completely set it up again from scratch, which made no difference (actually twice, the second time as you can't turn off the 2.4GHz later on). Alas the marginally more recent firmware I added (before my original post, it didn't change anything speed related) meant I could only administer it from the Ethernet side, which was a little annoying and sorted by a Pi4...

It sounds like the custom tweaks you've made are the cause of the issues.
You should run the AX6000 by itself with as little alterations from the stock settings to determine if the unit is defective.
This might mean starting over fresh with the AX6000.

If you did not GUI factory reset AFTER flashing from stock, this alone may be the cause of your woes.

The AC68 is very old and may be killing the setup.

 

[FredTheFrog]

388.4 presents the same problem with multiple IOT devices going offline more frequently than not.
Thinking to drop back to 388.2.2 which was stable for months.

 

[AntonK]

388.4 presents the same problem with multiple IOT devices going offline more frequently than not.
Thinking to drop back to 388.2.2 which was stable for months.

My (admittedly few) IoT devices are solid as a rock. This includes bulbs, smart plugs, watches, and clocks (variously on 2.4 and 5GHz bands).

 

[OakleyFreak]

My (admittedly few) IoT devices are solid as a rock. This includes bulbs, smart plugs, watches, and clocks (variously on 2.4 and 5GHz bands).

Mine also rock solid off of 86u and 86s as mesh

 

[FredTheFrog]

Mine also rock solid off of 86u and 86s as mesh

Mine are four RT-AX88U in an aiMesh configuration. 388.2_2 was very stable for many months, so I had no reservations about taking the 388.4_0 update. Until things started dropping offline yesterday. Different devices, different brands, different wifi chips, ESP8266, ESP32. Just finished rolling back all three WAPs and the router to 388.2_2 to see if the problems resolve.

Slowly, devices are beginning to come back online. The best thing would be if they STAY connected. Time will tell.

 

[BlueRadical]

Mine are four RT-AX88U in an aiMesh configuration. 388.2_2 was very stable for many months, so I had no reservations about taking the 388.4_0 update. Until things started dropping offline yesterday. Different devices, different brands, different wifi chips, ESP8266, ESP32. Just finished rolling back all three WAPs and the router to 388.2_2 to see if the problems resolve.

Slowly, devices are beginning to come back online. The best thing would be if they STAY connected. Time will tell.

I was having the same 2.4GHz issues with three IOT devices on 388.4 (garage door openers, and a baby monitor.) They would go at most a day and then just permanently drop until the router and device was rebooted (sometimes needing several reboots.)

I reverted to the previous firmware revision and I've had no issues in the week since.