Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[NiklasO]

Dirty upgrade from Beta1. Had to do install twice, but took the upgrade on the second attempt after I'd hard rebooted per router prompt...
Oddly, on the second successful attempt, got the same 'manual reboot required,' then seconds later flopped over to the normal sign in page?

It says manual reboot required if the timer runs out. Just wait a little bit longer and the page will load the login if/when the connection to the router comes back. It depend on how you connect (wifi, cable, wifi dfs scan until wifi available etc) and how fast your connection to the router reconnects but the timer will keep on running (and it will tell you to manually reboot if the router doesn't come back in time, but it eventually did for you so it loaded the login).

 

[scootertramp]

Updated from 3006.102.5 to 3006.102.6_beta2. Only oddity so far was one my my XT8's was slow
to stabilize. It is the only one of the three using a wireless backhaul.

A little over 24 hours running. Everything seems to be working fine.

 

[Untried3868]

So far so good on beta 2.

 

[RetroPas74]

Updates my AXE16000 to Merlin 3006.102.6_beta2 from 3006.102.4...

Sonos speakers are throwing continuously the following message:

Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2

Not sure why they won't connect anymore.
Any suggestions?

 

[penguin22]

Updates my AXE16000 to Merlin 3006.102.6_beta2 from 3006.102.4...

Sonos speakers are throwing continuously the following message:

Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2

Not sure why they won't connect anymore.
Any suggestions?

I had several IoT devices with stable connection issues. The one setting change with the biggest effect was disabling 11b support in Wireless \ Professional. If you are able to, and most people should be unless you have extremely old devices, I would try disabling 11b and see if connection stability improves.

 

[David Cavalli]

If it`s a PC, that PC while in sleep mode might be dropping its Ethernet link to 10 Mbps, for power savings (it only gets what is needed to still handle WOL packets).

Nov 21 04:42:48 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link DOWN.
Nov 21 04:42:50 kernel: eth3 (Int switch port: 2) (Logical Port: 2) (phyId: 3) Link Up at 10 mbps full duplex

If I read the System Log correctly, my stepson shut off his computer (assumption, because it doesn't list online) at 4am and the link reported DOWN. Almost immediately later, eth3 (which I assume is LAN3, where it currently sits) is Up at 10 mbps. He's still asleep and the Ethernet Ports shows the yellow 10 Mbps status.

Nov 21 02:00:08 SIG_UPDATE: current sig : 2482
Nov 21 02:00:08 SIG_UPDATE: latest sig : 2482

I'm trying to use the System Log to find any anomalies that lead up to the router crash. Skipping the Link DOWN items, I see many sets of {Disassoc, Deauth_ind, Auth, Assoc} sets in the log when some IoT devices, tablets, etc. lose/reset connectivity. The only item that stands out other than those is the above "SIG_UPDATE" entries, which don't seem to change the value. Anything important?

 

[penguin22]

One observation I had is that my System Message log was growing absurdly fast, with logrotate not even able to keep up. I found that the primary culprit was kernel messages relating to Smart Connect and Roaming Assist and client connections and disconnections. This to the tune of millions of lines, which aren't even visible within the GUI. This seems to be noise even though the actions are occurring since things are functioning, so I lowered the log level to warnings only "dmesg -n 4" (as well as by adding to services-start) and no longer see the uncontrolled messages log growth.

Total lines in /opt/var/log/messages: ~1,437,640
Top offenders:

WLC_SCB_DEAUTHORIZE error (-30) → 279,849
CFG80211-ERROR wl_cfg80211_change_station → 279,849
SBF: dhdX INIT (multiple MACs) → ~145,408 + several 65,536 blocks
blog_get_dstentry_by_id → 131,072
WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30 → 65,536
Other kernel spam combined → >95% of log content

Log file size before fix: 124 MB in one day

I believe that this can be attributed to some IoT devices that are constantly flapping, so it may warrant some creativity on my part to address the behavior (or ignoring it since with debug logs suppressed, everything is connected stably).

 

[muffintastic]

How's BETA2 BE86U? Still on BETA1.

 

[Ripshod]

I don't post often about problems because generally I don't have any. But, this is a new one to me

Nov 22 08:10:59 ripshod hostapd: wl0.2: STA 10:52:1c:fa:d8:04 IEEE 802.11: disassociated
Nov 22 08:10:59 ripshod hostapd: wl0.2: STA f4:cf:a2:27:e1:b5 IEEE 802.11: disassociated
Nov 22 08:10:59 ripshod hostapd: wl0.2: STA 1c:e8:9e:a7:83:6e IEEE 802.11: disassociated
Nov 22 08:10:59 ripshod hostapd: wl0.2: STA 10:52:1c:fa:cc:a2 IEEE 802.11: disassociated
Nov 22 08:10:59 ripshod hostapd: wl0.2: STA 10:52:1c:fc:0f:41 IEEE 802.11: disassociated
Nov 22 08:11:04 ripshod acsd: wl0: COEX: downgraded chanspec 0x190b to 0x100d: channel 6 used by exiting BSSs

Log stops there.
(That's all five 2.4GHz IoT devices disconnecting, I have fixed channel 13 which is clear of anyone else)
Followed immediately with total wifi collapse. The log just stopped. Had to power cycle to get it all working again
Being on a mobile I couldn't look closer, but if it happens again I'll fire up the notebook and see what happens there.

 

[SANdood]

On the RT-BE92U Network Map page, I notice that the tabs are missing under the System Status segment on the right - it only shows what is on the "Status" page. Shouldn't there be a page for "Wireless"?

TBH, I don't remember if it was there on the stock firmware before I upgraded this new router to Merlin...

 

[lgkahn]

working fine. on gtaxe16000 reset on upgrade..
minor interface bug
i have 5g 1st wifi band disabled as i use that with upstairs router and use the 5g 2nd wifi here..

on the network tools/ site survey its telling me the 2.4 ghz interface is disabled.. which it obviously is not..

thanks

@merlin

 

[Wayne Hutchinson]

Question, looking through my router system log file i see this msg,

Nov 22 10:09:51 Skynet: Startup Initiated... ( skynetloc=/tmp/mnt/Skynet/skynet )
Nov 22 10:09:51 Skynet: [✘] Private WAN IP Detected 192.168.1.71 - Please Put Your Modem In Bridge Mode / Disable CG-NAT

I have checked my AT&T Fiber modem and all WiFi's are disabled, Why do I get this msg?

Thanks

 

[dave14305]

Question, looking through my router system log file i see this msg,

Nov 22 10:09:51 Skynet: Startup Initiated... ( skynetloc=/tmp/mnt/Skynet/skynet )
Nov 22 10:09:51 Skynet: [✘] Private WAN IP Detected 192.168.1.71 - Please Put Your Modem In Bridge Mode / Disable CG-NAT

I have checked my AT&T Fiber modem and all WiFi's are disabled, Why do I get this msg?

This isn’t related to the beta, it’s a Skynet question. You don’t have a public WAN IP. The ISP device must have a public IP and you’re in double-nat. Has nothing to do with the modem WiFi specifically.

 

[RMerlin]

On the RT-BE92U Network Map page, I notice that the tabs are missing under the System Status segment on the right - it only shows what is on the "Status" page. Shouldn't there be a page for "Wireless"?

TBH, I don't remember if it was there on the stock firmware before I upgraded this new router to Merlin...

Wireless settings were reorganized by Asus to handle SDN/Guest Network Pro/Network definitions.

 

[scootertramp]

On the RT-BE92U Network Map page, I notice that the tabs are missing under the System Status segment on the right - it only shows what is on the "Status" page. Shouldn't there be a page for "Wireless"?

TBH, I don't remember if it was there on the stock firmware before I upgraded this new router to Merlin...

It has changed. New layout from stock firmware to current
I maybe wrong but I think the new network tab replaces what we use to see for wireless on network map.

 

[ColinTaylor]

Nov 22 08:11:04 ripshod acsd: wl0: COEX: downgraded chanspec 0x190b to 0x100d: channel 6 used by exiting BSSs

(That's all five 2.4GHz IoT devices disconnecting, I have fixed channel 13 which is clear of anyone else)

You haven't really set a fixed channel because you're using 20/40 bandwidth. 13@40 and 13@20 are treated as different "channels". So the message is saying that an existing BSS was detected on channel 6 (which just overlaps with 13@40) so it changed to 13@20.

 

[Ripshod]

You haven't really set a fixed channel because you're using 20/40 bandwidth. 13@40 and 13@20 are treated as different "channels". So the message is saying that an existing BSS was detected on channel 6 (which just overlaps with 13@40) so it changed to 13@20.

But all wifi SSIDs died at that point, and hadn't returned after 15 minutes. Logging died too. So if it is the channel changing it appears (to me) the firmware/drivers couldn't handle it.

 

[Ripshod]

Shouldn't there be a page for "Wireless"?

It has changed

Has it? (BTW the image you posted isn't relevant)

Probably only for the one model.