Release Asuswrt-Merlin 388.1 is now available for all supported Wifi 6 models

[AdamW]

after uploading version 388.1 on my RT-AX86U on all TVs still disconnects netflix, disney chanel, hbo etc. after restoring version 386.7_2 everything is ok

 

[392198523]

Hi, I have an AX86U upgraded to 388.1 and a AC86U upgraded to 386.9, both from 386.7_2.

After the upgrade, both of them appears to consume much more CPU than 386.7_2. It consumes 100% CPU and becomes unstable at about 300Mbps. Tx/Rx rate stutters while packet loss increases, as well as Wifi Bandwidth decreases.

I have tried reset to factory and the issue persists. Reverted to 386.7_2 solves the issue for me.

 

[Dabombber]

IPv6 support for asuscomm ddns doesn't work with ISP's IPv4 PPPoE and HE's IPv6 6in4 tunnel. It seems to be a bug of the ddns client, not ddns provider. Log says

ddns: ppp0 has not yet obtained an WAN IPv6 address.

and ddns would refuse to update. There is no IPv6 from ISP's IPv4 PPPoE so obviously it can't find an IPv6 address. Temporary workaround is simply disabling IPv6 support in ddns setting so at least it updates ddns with IPv4 address.

Otherwise dirty upgraded from 386.7_2 to 388.1 with no problems at all. Thanks again for this wonderful firmware.

I'm getting the same thing.

Is the logic for this right?

#ifdef RTCONFIG_IPV6
    if (nvram_get_int("ddns_ipv6_update")
        && ipv6_enabled() && (_get_ipv6_addr(wan_ifname, ip6_addr, sizeof(ip6_addr)) != 0))
    {
        logmessage("ddns", "%s has not yet obtained an WAN IPv6 address.(%d)", wan_ifname, ddns_check_retry);
        /* Trigger watchdog when start fails */
        nvram_unset("ddns_updated");
        nvram_set("ddns_return_code", "ddns_query"); /* for Retry mechanism */
        nvram_set("ddns_return_code_chk", "-1");
        return -1;
    }
#endif

cat /proc/net/if_inet6
fe80000000000000xxxxxxxxxxxxxxxx 09 40 20 80     eth1
fe80000000000000xxxxxxxxxxxxxxxx 0f 0a 20 80     ppp0
fe80000000000000xxxxxxxxxxxxxxxx 03 40 20 80     ifb1
fe80000000000000xxxxxxxxxxxxxxxx 0e 40 20 80      br0
fe80000000000000xxxxxxxxxxxxxxxx 0b 40 20 80    vlan1
fe80000000000000xxxxxxxxxxxxxxxx 07 40 20 80     eth0
fe80000000000000xxxxxxxxxxxxxxxx 0a 40 20 80     eth2
fe80000000000000xxxxxxxxxxxxxxxx 02 40 20 80     ifb0
fe80000000000000xxxxxxxxxxxxxxxx 08 40 20 c0    dpsta
fe80000000000000xxxxxxxxxxxxxxxx 06 40 20 c0      agg
fe80000000000000xxxxxxxxxxxxxxxx 04 40 20 c0     fwd0
fe80000000000000xxxxxxxxxxxxxxxx 05 40 20 80     fwd1
xxxxxxxxxxxxxx000000000000000001 0e 40 00 80      br0
00000000000000000000000000000001 01 80 10 80       lo

 

[Robaye]

This is just what my new AX86U was waiting for. Thanks for your work

Mine, too!!

 

[penguin22]

Quick update to report that after a full 7 days, manually setting the channels has fully resolved any stability issues that I was having. I use SmartConnect to keep my 2.4GHz and 5GHz SSID the same and having the ability to go about the house letting devices connect between routers as needed and it's been working perfectly now.

 

[Damit1]

Longest uptime in long time, no issues whatsoever.
AX56U is in alpha for the 388.2 for almost 2 weeks, no issues observed.

Only the AX56U ports now show status is observed, but that seems to be core-ASUS stock issue, will let it be.
Thank you!

 

[Dedel66]

Quick update to report that after a full 7 days, manually setting the channels has fully resolved any stability issues that I was having. I use SmartConnect to keep my 2.4GHz and 5GHz SSID the same and having the ability to go about the house letting devices connect between routers as needed and it's been working perfectly now.

Would be nice if you add your model(s). Eg. add a signature with your setup.
THANKS!

 

[srkbear]

Hi @RMerlin any plans to add the new ROG GT6 to your list of supported models in the future? I just purchased a pair, but the “initial” firmware (22233) is a mess when it comes to playing nice with other mesh broadcasters in their Wi-Fi 6 line.

I have a GT-AX11000 Pro as my main router, with your 388.1 firmware installed. I had been using five ZenWifi XT9s with native ASUS firmware (22068) as mesh nodes on a wireless backhaul, using channel 173 on the U-NII-4 spectrum on the 160mhz channel width with excellent results. Seamlessly, to be frank—I’m delighted!

I thought I would try replacing a couple of my XT9s with GT6s in a couple of rooms where I have a number of streaming/gaming clients, to take advantage of their 4X4 antenna configurations and their proposed 4804 mpbs throughout on the 5GHz-1 band (as opposed to the 2X2 configuration on the XT9s).

On initial setup, with the shipped firmware, they seemed to work beautifully. The native firmware was something in the 3.0.0.4.388.21XXX range—I only saw it briefly before I made the mistake of reflexively updating to the 22233 release. Strangely, the ASUS website claims that this version is the “initial firmware release”, but that is clearly not true, based on what mine shipped with.

As soon as I did the firmware update, the GT6s refused to connect to my GT-AX11000 Pro with your 388.1 build, despite showing that they were recognized and set up without incident. They would only bind to one of the other XT9 nodes, with a weak connection, and when I ran optimization they would drop off entirely and stay indefinitely in the flashing blue light of death.

I’ve searched everywhere trying to locate that 21XXX stock firmware version without any luck. I have no choice but to either return them or wait for a future firmware release either for your GT-AX11000 Pro build or for the GT6s themselves. If you have any troubleshooting suggestions I’d appreciate it!

As an aside, do you have any plans to add the 160mhz channel width and the U-NII-4 channels to your Wi-Fi Radar solution in the future?

Thanks as always for all the great work you do.

—Steve Klemow

 

[RMerlin]

Hi @RMerlin any plans to add the new ROG GT6 to your list of supported models in the future?

I can't speculate about future model support.

As an aside, do you have any plans to add the 160mhz channel width and the U-NII-4 channels to your Wi-Fi Radar solution in the future?

WiFi Radar is a closed source soluton developed by Broadcom, and is outside of my control.

 

[penguin22]

Would be nice if you add your model(s). Eg. add a signature with your setup.
THANKS!

AX86U as the main router running 388.1 and AX86U AiMesh node running stock. I am hard-wired between the 2 about 200' apart on opposite ends of a ranch style house.

 

[John Fitzgerald]

Hi @RMerlin any plans to add the new ROG GT6 to your list of supported models in the future? I just purchased a pair, but the “initial” firmware (22233) is a mess when it comes to playing nice with other mesh broadcasters in their Wi-Fi 6 line.

I have a GT-AX11000 Pro as my main router, with your 388.1 firmware installed. I had been using five ZenWifi XT9s with native ASUS firmware (22068) as mesh nodes on a wireless backhaul, using channel 173 on the U-NII-4 spectrum on the 160mhz channel width with excellent results. Seamlessly, to be frank—I’m delighted!

I thought I would try replacing a couple of my XT9s with GT6s in a couple of rooms where I have a number of streaming/gaming clients, to take advantage of their 4X4 antenna configurations and their proposed 4804 mpbs throughout on the 5GHz-1 band (as opposed to the 2X2 configuration on the XT9s).

On initial setup, with the shipped firmware, they seemed to work beautifully. The native firmware was something in the 3.0.0.4.388.21XXX range—I only saw it briefly before I made the mistake of reflexively updating to the 22233 release. Strangely, the ASUS website claims that this version is the “initial firmware release”, but that is clearly not true, based on what mine shipped with.

As soon as I did the firmware update, the GT6s refused to connect to my GT-AX11000 Pro with your 388.1 build, despite showing that they were recognized and set up without incident. They would only bind to one of the other XT9 nodes, with a weak connection, and when I ran optimization they would drop off entirely and stay indefinitely in the flashing blue light of death.

I’ve searched everywhere trying to locate that 21XXX stock firmware version without any luck. I have no choice but to either return them or wait for a future firmware release either for your GT-AX11000 Pro build or for the GT6s themselves. If you have any troubleshooting suggestions I’d appreciate it!

As an aside, do you have any plans to add the 160mhz channel width and the U-NII-4 channels to your Wi-Fi Radar solution in the future?

Thanks as always for all the great work you do.

—Steve Klemow

The stock shipping firmware is located normally on the box and the tag that is on the router.

 

[LarryR]

So running the gnuton fork on my XT8. Seems pretty stable so far. Can anyone tell me what these mean from the log:

Jan 21 17:28:28 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 17:28:29 bsd: bsd: STA:0c:02:bd:fd:d0:42 no response
Jan 21 17:28:29 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 17:28:29 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=99, status=1, mac=dd:07:50:6f:9a:16
Jan 21 17:28:29 bsd: bsd: BSS Transit Response: STA reject
Jan 21 17:28:29 bsd: bsd: Skip STA:0c:02:bd:fd:d0:42 reject BSSID
Jan 21 20:56:33 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 20:56:33 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=e, status=1, mac=00:00:00:00:00:00
Jan 21 20:56:33 bsd: bsd: BSS Transit Response: not for token 9a
Jan 21 20:56:33 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 20:56:34 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=9a, status=6, mac=34:0d:04:42:1a:35
Jan 21 20:56:34 bsd: bsd: BSS Transit Response: not for token 9b
Jan 21 21:09:18 bsd: bsd: Sending act Frame to ba:9e:a7:03:40:e4 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=f, status=0, mac=04:42:1a:35:44:94
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: not for token 9c
Jan 21 21:09:18 bsd: bsd: Sending act Frame to ba:9e:a7:03:40:e4 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=9c, status=1, mac=00:00:00:00:00:00
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: not for token 9d
Jan 22 03:10:10 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 03:10:12 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 03:10:12 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 03:10:13 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 04:13:13 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 04:13:14 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 04:13:14 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 04:13:16 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 09:37:41 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 09:37:41 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=10, status=0, mac=04:42:1a:35:44:94
Jan 22 09:37:41 bsd: bsd: BSS Transit Response: not for token a2
Jan 22 09:37:41 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 09:37:42 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=11, status=0, mac=04:42:1a:35:44:94
Jan 22 09:37:42 bsd: bsd: BSS Transit Response: not for token a3
Jan 22 11:59:20 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 11:59:20 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=a4, status=6, mac=34:0d:04:42:1a:35
Jan 22 11:59:20 bsd: bsd: BSS Transit Response: STA reject
Jan 22 11:59:20 bsd: bsd: Skip STA:0c:02:bd:fd:d0:42 reject BSSID
Jan 22 12:02:56 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 12:02:58 bsd: bsd: STA:0c:02:bd:fd:d0:42 no response

 

[bartj12]

So running the gnuton fork on my XT8. Seems pretty stable so far. Can anyone tell me what these mean from the log:

Jan 21 17:28:28 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 17:28:29 bsd: bsd: STA:0c:02:bd:fd:d0:42 no response
Jan 21 17:28:29 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 17:28:29 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=99, status=1, mac=dd:07:50:6f:9a:16
Jan 21 17:28:29 bsd: bsd: BSS Transit Response: STA reject
Jan 21 17:28:29 bsd: bsd: Skip STA:0c:02:bd:fd:d0:42 reject BSSID
Jan 21 20:56:33 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 20:56:33 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=e, status=1, mac=00:00:00:00:00:00
Jan 21 20:56:33 bsd: bsd: BSS Transit Response: not for token 9a
Jan 21 20:56:33 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 20:56:34 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=9a, status=6, mac=34:0d:04:42:1a:35
Jan 21 20:56:34 bsd: bsd: BSS Transit Response: not for token 9b
Jan 21 21:09:18 bsd: bsd: Sending act Frame to ba:9e:a7:03:40:e4 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=f, status=0, mac=04:42:1a:35:44:94
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: not for token 9c
Jan 21 21:09:18 bsd: bsd: Sending act Frame to ba:9e:a7:03:40:e4 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=9c, status=1, mac=00:00:00:00:00:00
Jan 21 21:09:18 bsd: bsd: BSS Transit Response: not for token 9d
Jan 22 03:10:10 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 03:10:12 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 03:10:12 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 03:10:13 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 04:13:13 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 04:13:14 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 04:13:14 bsd: bsd: Sending act Frame to 28:16:a8:64:24:1b with transition target eth5 ssid 04:42:1a:34:83:24
Jan 22 04:13:16 bsd: bsd: STA:28:16:a8:64:24:1b no response
Jan 22 09:37:41 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 09:37:41 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=10, status=0, mac=04:42:1a:35:44:94
Jan 22 09:37:41 bsd: bsd: BSS Transit Response: not for token a2
Jan 22 09:37:41 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 09:37:42 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=11, status=0, mac=04:42:1a:35:44:94
Jan 22 09:37:42 bsd: bsd: BSS Transit Response: not for token a3
Jan 22 11:59:20 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 11:59:20 bsd: bsd: BSS Transit Response: ifname=eth5, event=156, token=a4, status=6, mac=34:0d:04:42:1a:35
Jan 22 11:59:20 bsd: bsd: BSS Transit Response: STA reject
Jan 22 11:59:20 bsd: bsd: Skip STA:0c:02:bd:fd:d0:42 reject BSSID
Jan 22 12:02:56 bsd: bsd: Sending act Frame to 0c:02:bd:fd:d0:42 with transition target eth4 ssid 04:42:1a:34:83:20
Jan 22 12:02:58 bsd: bsd: STA:0c:02:bd:fd:d0:42 no response

These are errors caused by Smart Connect. Just turn it off as it does not bring much value.
I believe this was discussed before if you need more details.

 

[LarryR]

My log is now full of these... I there a fix needed? Reboot? Or no real issue?

Jan 23 17:04:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:04:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:05:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:06:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:07:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:09:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:10:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:10:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:00 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:07 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:09 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:12:09 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)

 

[ColinTaylor]

My log is now full of these... I there a fix needed? Reboot? Or no real issue?

Jan 23 17:04:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:04:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:05:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:06:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:07:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:08:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:09:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:10:23 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:10:44 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:00 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:07 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:11:09 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)
Jan 23 17:12:09 dnsmasq-dhcp[3575]: failed to write /var/lib/misc/dnsmasq.leases: No space left on device (retry in 60 s)

If you're running GNUton's fork on an XT8 it's probably best to ask your question in the GNUton thread as this thread is about the standard Merlin builds.

 

[MotoChooch]

Having a weird issue with 388.1 Search didn't come up with much. I can't speed test beyond 500mbps (ish). Not on the 2.5g port which previously tested over 2g/2g (ISP 2g plan), and not on the gig ports. Speed test on the router itself is fine.

Direct from my pc to the ONT gives full speed. Is this a known issue? I'm about to go back to the stock firmware but I wanted to see if I was alone in this.

Edit: Just realized I never did any kind of reset after the update so I'm going to try that tonight. Was coming from the previous merlin firmware which worked a treat.

Update: Put the stock firmware back and it's working normally now. I think I'm done with Merlin for now, maybe I'll revisit in the future.

 

[Kabouter Plop]

I wish i could cable test my wan port cable to see if any data lines drop out im having mine drop out with connection in the wall but not seperate cable, been plagued by it for years found out it was wired incorrectly but now its starting to fail again as if there is a bad cable in the wall

 

[Gar]

I need to upgrade the firmware of my router, but will wait for next release I think. Too many reports here of problems with the Asus RT-AX88U

Mine has been great since day 1.

 

[samfisher]

Still having random reboots from the kernel panic bug on my AX86U, anyone got a solution on what to do?

 

[Kabouter Plop]

Still having random reboots from the kernel panic bug on my AX86U, anyone got a solution on what to do?

Thats quite bad something causing your router to be unstable hardware/software failure