Beta Asuswrt-Merlin 3006.102.2 Beta is now available for Wifi 7 devices

[Blacklistedcard]

Just bought the BE98Pro and put the beta firmware on it. Moved my AX88 to the other side of the house in AI Mesh. Works great no issue(s) like my trusty AX88 when it was the main AP. Nice to have 2.5gig going to the rogers modem.

Some point in time I will do the MLO setup.

 

[fka]

No. That`s Asus' to investigate and/or fix.

Asus support sent me RT-AX88U_PRO_3.0.0.6_102_35853-g5ee6803_441-g8b5e0_nand_squashfs.pkgtb for the AX88U Pro
Still no joy getting getting the IPTV working so the BE88U is going back.

Thanks again Merlin. You and asuswrt-merlin are the reason I've stuck with this kit for last last 10 years!

 

[RMerlin]

Here you go..first thing I did was to re-enable detailed logging after clearing the log. Then I disabled the IoT network, and tried to access the internet on my browser. When that finally timed out, I saved the log.

Hope this helps.

Asus's engineer reworked my initial patch to address things at a lower level. Can you test this build please?

RT-BE96U_3006_102.2_beta2-g157580b179_nand_squashfs.pkgtb

 

[RogerSC]

Asus's engineer reworked my initial patch to address things at a lower level. Can you test this build please?

RT-BE96U_3006_102.2_beta2-g157580b179_nand_squashfs.pkgtb

Giving this build a shot. Flashed it and turned off IoT network, still had internet on remaining networks. Toggled the IoT network switch a couple of times, just to be sure that the first time wasn't a fluke. Worked consistently. No problems yet.

The only caveat is that I've turned on MLO since I saw this problem before. Shouldn't have any effect, but thought that I should mention that.

Anyways, looks good. I'm continuing to use this new build, until I have reason not to. Nice to be able to turn off the IoT network, since I'm not using it.

 

[RMerlin]

Giving this build a shot. Flashed it and turned off IoT network, still had internet on remaining networks. Toggled the IoT network switch a couple of times, just to be sure that the first time wasn't a fluke. Worked consistently. No problems yet.

Ok, thanks for the confirmation.

 

[RogerSC]

Since turning on MLO on the RT-BE96U, I've been seeing the messages shown below in the router system log. I've seen no problems with our wireless, no disconnects, streaming has been great, etc., but the "reject BSSID"'s and "STA reject"'s caught my eye. Wondering if these are anything to worry about, or just events from which the router has recovered?

Oct 23 03:22:57 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:22:58 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=1, status=6, mac=34:10:e8:9c:25:04
Oct 23 03:22:58 bsd: bsd: BSS Transit Response: STA reject
Oct 23 03:22:58 bsd: bsd: Skip STA:f6:95:54:83:c9:b7 reject BSSID
Oct 23 03:31:25 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:31:26 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 03:31:26 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:31:26 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=3, status=6, mac=34:10:e8:9c:25:04
Oct 23 03:31:26 bsd: bsd: BSS Transit Response: STA reject
Oct 23 03:31:26 bsd: bsd: Skip STA:f6:95:54:83:c9:b7 reject BSSID
Oct 23 03:43:39 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:43:40 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 03:43:40 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:43:41 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 03:50:22 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 03:50:23 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=6, status=6, mac=34:10:e8:9c:25:04
Oct 23 03:50:23 bsd: bsd: BSS Transit Response: STA reject
Oct 23 03:50:23 bsd: bsd: Skip STA:02:3a:c3:1a:6a:d0 reject BSSID
Oct 23 04:06:36 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:06:37 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=7, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:06:37 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:06:37 bsd: bsd: Skip STA:02:3a:c3:1a:6a:d0 reject BSSID
Oct 23 04:15:44 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:15:45 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=8, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:15:45 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:15:45 bsd: bsd: Skip STA:02:3a:c3:1a:6a:d0 reject BSSID
Oct 23 04:24:21 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:24:22 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=9, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:24:22 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:24:22 bsd: bsd: Skip STA:02:3a:c3:1a:6a:d0 reject BSSID
Oct 23 04:31:49 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:31:49 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=a, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:31:49 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:31:49 bsd: bsd: Skip STA:02:3a:c3:1a:6a:d0 reject BSSID
Oct 23 04:35:05 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:35:06 bsd: bsd: STA:02:3a:c3:1a:6a:d0 no response
Oct 23 04:35:06 bsd: bsd: Sending act Frame to 02:3a:c3:1a:6a:d0 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:35:07 bsd: bsd: STA:02:3a:c3:1a:6a:d0 no response
Oct 23 04:46:04 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:46:05 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=d, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:46:05 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:46:05 bsd: bsd: Skip STA:f6:95:54:83:c9:b7 reject BSSID
Oct 23 04:55:32 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:55:33 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 04:55:33 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 04:55:33 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=f, status=6, mac=34:10:e8:9c:25:04
Oct 23 04:55:33 bsd: bsd: BSS Transit Response: STA reject
Oct 23 04:55:33 bsd: bsd: Skip STA:f6:95:54:83:c9:b7 reject BSSID
Oct 23 05:01:05 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 05:01:06 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 05:01:06 bsd: bsd: Sending act Frame to f6:95:54:83:c9:b7 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 05:01:07 bsd: bsd: STA:f6:95:54:83:c9:b7 no response
Oct 23 05:43:31 bsd: bsd: Sending act Frame to 08:e6:89:cf:49:9a with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 05:43:32 bsd: bsd: STA:08:e6:89:cf:49:9a no response
Oct 23 05:43:32 bsd: bsd: Sending act Frame to 08:e6:89:cf:49:9a with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 05:43:32 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=13, status=6, mac=34:10:e8:9c:25:04
Oct 23 05:43:32 bsd: bsd: BSS Transit Response: STA reject
Oct 23 05:43:32 bsd: bsd: Skip STA:08:e6:89:cf:49:9a reject BSSID
Oct 23 08:02:28 bsd: bsd: Sending act Frame to ce:8b:39:f8:62:cb with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 08:02:28 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=14, status=6, mac=34:10:e8:9c:25:04
Oct 23 08:02:28 bsd: bsd: BSS Transit Response: STA reject
Oct 23 08:02:28 bsd: bsd: Skip STA:ce:8b:39:f8:62:cb reject BSSID
Oct 23 09:27:56 bsd: bsd: Sending act Frame to f0:05:1b:e4:2c:87 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 09:27:57 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=15, status=0, mac=e8:9c:25:04:88:10
Oct 23 09:27:57 bsd: bsd: BSS Transit Response: STA accept
Oct 23 09:57:08 bsd: bsd: Sending act Frame to f0:05:1b:e4:2c:87 with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 09:57:08 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=16, status=0, mac=e8:9c:25:04:88:10
Oct 23 09:57:08 bsd: bsd: BSS Transit Response: STA accept
Oct 23 11:02:52 bsd: bsd: Sending act Frame to 08:e6:89:cf:49:9a with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 11:02:52 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=17, status=6, mac=34:10:e8:9c:25:04
Oct 23 11:02:52 bsd: bsd: BSS Transit Response: STA reject
Oct 23 11:02:52 bsd: bsd: Skip STA:08:e6:89:cf:49:9a reject BSSID
Oct 23 11:07:08 bsd: bsd: Sending act Frame to 08:e6:89:cf:49:9a with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 11:07:08 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=18, status=6, mac=34:10:e8:9c:25:04
Oct 23 11:07:08 bsd: bsd: BSS Transit Response: STA reject
Oct 23 11:07:08 bsd: bsd: Skip STA:08:e6:89:cf:49:9a reject BSSID
Oct 23 11:30:59 bsd: bsd: Sending act Frame to 08:e6:89:cf:49:9a with transition target wl0 ssid e8:9c:25:04:88:10
Oct 23 11:30:59 bsd: bsd: BSS Transit Response: ifname=wl1, event=156, token=19, status=6, mac=34:10:e8:9c:25:04
Oct 23 11:30:59 bsd: bsd: BSS Transit Response: STA reject
Oct 23 11:30:59 bsd: bsd: Skip STA:08:e6:89:cf:49:9a reject BSSID

 

[baller54]

Oooh new RT-BE96U firmware came out today, finally! 1st update since April.

Release - ASUS RT-BE96U Firmware version 3.0.0.6.102_37024 (10/23/2024)

Click here for firmware download page: ASUS RT-BE96U Firmware 3.0.0.6.102_37024 *Please be advised that due to an architecture upgrade in AiMesh, we highly discourage downgrading to earlier firmware versions as it may result in connectivity problems. If you experience any difficulties, we...

www.snbforums.com

 

[nfshp253]

Flashed the BETA firmware onto my BE7200 yesterday and unfortunately it seemed to suffer a "catastrophic" failure today. The router would bootloop, show the power, the 2 wireless LEDs, the WAN LED and a red Internet LED before restarting and cycling though the same thing over and over again. I tried disconnecting everything from the router (USB, SFP+, LAN, WAN) and restarting, but it just bootloops after showing Power and the WiFi LEDs.

I had to do a hard reset of the router (holding the WPS and turning on the power). After running the setup wizard, everything started working again. Temporarily upgraded to the official 3.0.0.6.102_33928 for stability (hopefully this doesn't crash in the same way).

 

[Ripshod]

Flashed the BETA firmware onto my BE7200 yesterday and unfortunately it seemed to suffer a "catastrophic" failure today. The router would bootloop, show the power, the 2 wireless LEDs, the WAN LED and a red Internet LED before restarting and cycling though the same thing over and over again. I tried disconnecting everything from the router (USB, SFP+, LAN, WAN) and restarting, but it just bootloops after showing Power and the WiFi LEDs.

I had to do a hard reset of the router (holding the WPS and turning on the power). After running the setup wizard, everything started working again. Temporarily upgraded to the official 3.0.0.6.102_33928 for stability (hopefully this doesn't crash in the same way).

Did you perform a factory reset after installing this beta?

 

[nfshp253]

No I didn't. I ran the alpha for a few days before going to the beta. I've used Merlin firmwares for at least the last 8 years and never did a factory reset after flashing firmwares. I guess I should make that a thing going forward.

 

[matthew_eli]

Hi, RT-BE86U here with 3006.102.2beta1. It seems the DNS Director page is broken. I tried to edit the settings and I saw there were multiple Guest/IoT networks duplicated or blank
Now the DNS Director page is not loaded correctly, with the following error:

Uncaught Reference error: deviceVendor is not defined

 

[RMerlin]

Hi, RT-BE86U here with 3006.102.2beta1. It seems the DNS Director page is broken. I tried to edit the settings and I saw there were multiple Guest/IoT networks duplicated or blank
Now the DNS Director page is not loaded correctly, with the following error:

Uncaught Reference error: deviceVendor is not defined

What Guest Networks do you have defined? Any VLANs?

 

[matthew_eli]

What Guest Networks do you have defined? Any VLANs?

I enabled IoT and classic guest network, both on separate subnet; VLAN 52 and 53 assigned

EDIT: in the DNSDirector.asp there is the same typo deviceVender found before for GT-BE98

EDIT2: Editing the deviceVender to deviceVendor and mounting the new webpage does not fix the issue

 

[Frisswinter123]

@RMerlin looking forward to merlin support if you're supporting BQ16 and BQ16 Pro in the future.

 

[matthew_eli]

I enabled IoT and classic guest network, both on separate subnet; VLAN 52 and 53 assigned

View attachment 62139

EDIT: in the DNSDirector.asp there is the same typo deviceVender found before for GT-BE98

EDIT2: Editing the deviceVender to deviceVendor and mounting the new webpage does not fix the issue

EDIT 3: if I fix deviceVender entries in deviceVendor (3 occurences) at least the page does not get stuck! But the entries of the guest network would be duplicated anyway @RMerlin

 

[swejuggalo]

Anyone else noticed things going a bit weird at DTS? AX88U was fine (scribe logrotate still worked, VPNs alive and so on), but BE88U needed a reboot to fully work (failing scribe, no VPNs and such). Identical setup, as far as the firmware differences allowed.
Skynet, Diversion, Scribe (with UI), ScMerlin and some part of the integrated AMTM components (like LED control).

Attaching parts near the switch. It got a new IP assigned (I assume since it tried to update ddns) and everything but didn't recover by itself like the AX88U did.

 

[Kokorone]

Currently using the new 3006.102.2_beta1 on the RT-BE96U. Seeing some pretty major bugs with Smart Connect rules.

The Target Band options for both 5Ghz and 6Ghz exclusively have 2.4Ghz available. Routing is similarly busted

 

[RMerlin]

I enabled IoT and classic guest network, both on separate subnet; VLAN 52 and 53 assigned

View attachment 62139

EDIT: in the DNSDirector.asp there is the same typo deviceVender found before for GT-BE98

EDIT2: Editing the deviceVender to deviceVendor and mounting the new webpage does not fix the issue

Unable to reproduce here, works fine for me with the main IoT, a custom IoT and a custom Guest. The issue is specific to the RT-BE86U, which is based on a quite different GPL version from all other models. 102_36xxx has some major changes in how wifi is handled internally. sdn_rl now contains hidden entries for AiMesh backhaul/fronthaul that don't exist in previous versions.

This is why I usually request to have the same GPL version for all models, in this case after waiting for three months I gave up waiting, and decided to experiment with having a separate version.

 

[RMerlin]

Currently using the new 3006.102.2_beta1 on the RT-BE96U. Seeing some pretty major bugs with Smart

Smart Connect has been quirky for years. Any fix to it will have to come from Asus, that page is unchanged from stock firmware.

 

[joloxx9]

I have updated BE88U to beta and cannot acces router, got internet etc, just GUI is not working, no matter if I use IP or http://www.asusrouter.com/ any clues? I have tried restart and no luck, it is quite problematic now. Any help would be appreciated!

Openvpn not working either, is there anything I can do apart reset?