Release Asuswrt-Merlin 3006.102.3 is now available for WIfi 7 devices

[Noblistic]

I'm also running DDNS on my GT-BE98 Pro and having an issue where it doesn't automatically reconnect to my ISP for some reason; not sure that IPV6 makes a difference here, as it seemed to happen with just IPV4. However, if I simply go to WAN and hit "Apply" at the bottom, it will reconnect. Hopefully you can see it reconnect below from the System Log - General Log. I'm also getting inconsistent connection speeds to the router, where it's not always maintaining the 5764Mbps speed, and I have to reboot the router to usually get the full speed back; I believe this was also an issue with Asus' stock firmware, though.

Dec 31 18:04:12 wan: finish adding multi routes
Dec 31 18:04:12 openvpn-routing: Applying all killswitches
Dec 31 18:04:12 rc_service: udhcpc_wan 7419:notify_rc stop_ntpd
Dec 31 18:04:12 rc_service: udhcpc_wan 7419:notify_rc start_ntpd
Dec 31 18:04:12 rc_service: waitting "stop_ntpd"(last_rc:start_dhcp6c) via udhcpc_wan ...
Dec 31 18:04:13 ntpd: Started ntpd
Dec 31 18:04:13 WAN(0)_Connection: WAN was restored.

 

[visortgw]

There seems to be a bug in the DDNS config. Even although I have been able to succesfully establish an IPv6 WAN Address, I get the followinmg in the Logs
I'm using no-ip.com for DDNS.

watchdog: start ddns.
Jan 15 15:19:11 hostapd: wl1.1: STA a8:ca:77:c6:62:48 IEEE 802.11: disassociated
Jan 15 15:19:11 wlceventd: wlceventd_proc_event(645): wl1.1: Deauth_ind A8:CA:77:C6:62:48, status: 0, reason: Unspecified reason (1), rssi:-49
Jan 15 15:19:11 wlceventd: wlceventd_proc_event(685): wl1.1: Auth A8:CA:77:C6:62:48, status: Successful (0), rssi:-49
Jan 15 15:19:11 ddns: ppp0 has not yet obtained an WAN IPv6 address.(2)
Jan 15 15:19:11 ddns: current ipv6_service: dhcp6 | old ipv6_service: dhcp6
Jan 15 15:19:11 ddns: IP address, server and hostname have not changed since the last update.

RT-BE86U on Release 3006.102.3 I am connecting to my Provider (BT UK) via PPOE. Never had this issue on my RT-AX86U

It may be the combo of IPv6 and DDNS. DDNS works fine for me (as it always has) — I'm using IPv4 (no reason for me to move to IPv6 at this point) with DynDNS as DDNS provider.

 

[GMcD79]

It may be the combo of IPv6 and DDNS. DDNS works fine for me (as it always has) — I'm using IPv4 (no reason for me to move to IPv6 at this point) with DynDNS as DDNS provider.

DDNS works fine for me too if I disable "IPV6 Update" under the DDNS config settings. This was always set as "Enabled" for the RT-AX86U and it never complained
Not a big deal by any means.

 

[emwgee]

I am seeing a lot of these DEAUTHORIZE/DEAUTHENTICATE errors in the system log. Is it normal?


Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_del_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Jan 15 12:02:10 hostapd: wl3.2: STA 2b:ac:6e:71:6c:11 IEEE 802.11: disassociated
Jan 15 12:02:10 wlceventd: wlceventd_proc_event(645): wl3.2: Deauth_ind 2B:AC:6E:71:6C:11, status: 0, reason: Group key update timeout (10), rssi:-53
Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHORIZE error (-30)

 

[visortgw]

I am seeing a lot of these DEAUTHORIZE/DEAUTHENTICATE errors in the system log. Is it normal?


Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHORIZE error (-30)
Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_del_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHENTICATE_FOR_REASON err -30
Jan 15 12:02:10 hostapd: wl3.2: STA 2b:ac:6e:71:6c:11 IEEE 802.11: disassociated
Jan 15 12:02:10 wlceventd: wlceventd_proc_event(645): wl3.2: Deauth_ind 2B:AC:6E:71:6C:11, status: 0, reason: Group key update timeout (10), rssi:-53
Jan 15 12:02:10 kernel: CFG80211-ERROR) wl_cfg80211_change_station :
Jan 15 12:02:10 kernel: WLC_SCB_DEAUTHORIZE error (-30)

Just WiFi devices disconnecting and reconnecting...

 

[Noblistic]

I disabled DDNS and IPV6, but it didn't seem to make a difference. I rebuilt my config when I switched to Merlin, but I'd hate to have to do that after every update. Not sure what else to try. My only guess right now is that there's some kind of job that's not timing correctly upon startup, so hitting "Apply" gets it to try again when the timing is ready.

It looks like I can reload my config since I'm on Merlin already, so I'll try that next.

 

[RMerlin]

Asus' IPv6 DDNS implementation has always been quirky. I recommend to just disable IPv6 DDNS support.

 

[Noblistic]

Thanks for the suggestion, RMerlin. The config rebuild seems to have resolved the issue, and I don't think I forgot much of anything. Luckily, I didn't have a ton to recreate, but that will likely change over time.

My guess is that there was an incompatibility b/n the old and new config after they changed the network stack. Going forward, I think I'll be more hesitant to upgrade unless I see compelling reasons to in the release notes.

Regardless, I appreciate all the work you put into this project. Keep up the good work!

 

[rcfw]

Just wanted to quickly stop by and kindly ask if you could potentially send logs from a regular update (not recovery)?
System logs showing the update process would be incredibly valuable in situations like this, and may give a hint as to what the cause of friction is.

After failed update it changes my ssid to some random numbers and my guest networks multiply I’ve attached the image and router log

 

[ExtremeFiretop]

After failed update it changes my ssid to some random numbers and my guest networks multiply I’ve attached the image and router log

Something is deffinetly wrong with this, is this the entire log? The upgrade isn't even starting in that log.
You have constant logs indicating:

dhd_pktfwd_lut_lkup: pool 0 and unit 15 mismatched

Which to my understanding (someone correct me if I'm wrong) these repeated mismatch errors indicate the driver is hitting low-level issues when tearing down (or reinitializing) the wireless interface.

Seems like something in the broadcom driver is overwriting the interface: https://github.com/RMerl/asuswrt-me...s/net/wireless/brcm80211/brcmfmac/core.c#L784 This would likely indicate why your SSIDs are changing after the attempt.

You also have a log indicating a timeout action in the shutdown process:

Jan 16 01:02:56 kernel: CFG80211-ERROR) wl_cfg80211_del_iface :
Jan 16 01:02:56 kernel: timeout in waiting IF_DEL event

According to this: https://android.googlesource.com/ke...aa5/drivers/net/wireless/bcmdhd/wl_cfg80211.c
The broadcom driver would timeout after about 1.5 seconds and give the error your seeing. Considering the last interface it was trying to tear down was wl3.1 I would say a safe bet is the 2.4GHz is your issue.

Something is wrong with your wireless interface, run this command:

wl -i wl3.1 status

to report the status of the interface.
You can always try to manually take the interface offline before doing the upgrade via LAN:

wl -i wl3.1 down

Wouldn't be a solve to the issue as much as work around if it works.
What tool did you use to recover? The official ASUS recovery tool? Or tftpd64? TFTP has worked for me in the past when the ASUS tool has failed. (More info here: https://www.snbforums.com/threads/i...ition-mounting-in-read-only.89499/post-914083)

You can always check the health using @JGrana 's script to do a NAND check: https://www.snbforums.com/threads/a...available-for-select-models.81644/post-801367 but I would be seriously surprised if you have such bad luck to have bad blocks after only a few months of use.

 

[rcfw]

Something is deffinetly wrong with this, is this the entire log? The upgrade isn't even starting in that log.
You have constant logs indicating:



Which to my understanding (someone correct me if I'm wrong) these repeated mismatch errors indicate the driver is hitting low-level issues when tearing down (or reinitializing) the wireless interface.
Seems like something in the broadcom driver is overwriting the interface: https://github.com/RMerl/asuswrt-me...s/net/wireless/brcm80211/brcmfmac/core.c#L784

This would likely indicate why your SSIDs are changing after the attempt.
You also have a log indicating a timeout action in the shutdown process:



According to this: https://android.googlesource.com/ke...aa5/drivers/net/wireless/bcmdhd/wl_cfg80211.c
The broadcom driver would timeout after about 1.5 seconds and give the error your seeing. Considering the last interface it was trying to tear down was wl3.1 I would say a safe bet is the 2.4GHz is your issue.

Something is wrong with your wireless interface, run this command:

wl -i wl3.1 status

to report the status of the interface.
You can always try to manually take the interface offline before doing the upgrade via LAN:

wl -i wl3.1 down

Wouldn't be a solve to the issue as much as work around if it works.
What tool did you use to recover? The official ASUS recovery tool? Or tftpd64? TFTP has worked for me in the past when the ASUS tool has failed. (More info here: https://www.snbforums.com/threads/i...ition-mounting-in-read-only.89499/post-914083)

You can always check the health using @JGrana 's script to do a NAND check: https://www.snbforums.com/threads/a...available-for-select-models.81644/post-801367 but I would be seriously surprised if you have such bad luck to have bad blocks after only a few months of use.

I’ll send the whole log when I try again thanks for the info, I did also use the ASUS restore tool

 

[Armand28]

Recently updated to the latest Merlin version and I cannot find where to set my re-key interval. Searching help links me to the Network tab, but there is no where to set the WPA key interval there, and it’s not in the wireless or wireless>Professional tab. Anyone know where it went? Have a BE98-Pro running

3006_102.3_0​

I need to do this because I’m getting errors on all of my repeaters when re-keying happens which causes issues and disconnects. See attached image.

 

[nzwayne]

Upgraded over Beta level, no issues, smooth as silk. Myself & family flogged this update over weekend & then onwards, no issues, error free. Add-ons all seemed to work fine, just some minor GUI quirks on a couple. Thanks again @RMerlin , drink enablement coming your way, as a thank-you.

 

[SkippyP]

I haven't asked them because when we discussed a general roadmap last year, the plan was wait before moving existing devices to 3006 as the code was not mature enough yet. Hence the reason why I haven't asked for it yet, not because I didn't want to.

So, is it approaching a decent level of maturity where perhaps we can expect an announcement for AX device support soon?

 

[Ripshod]

RMerlin only made that statement a couple of days ago. Patience is the key.
Non-Pro AX devices won't be getting 3006.

 

[peltco]

i'm noticing that my AI Mesh network (all wireless) is virtually non-existing anymore since the latest update.

the logs show (many times) the following (not sure if it's related)

Jan 17 14:40:18 kernel: wfd_unregisterdevice Successfully unregistered ifidx 2 wfd_idx 1
Jan 17 14:40:18 kernel: ^[[0;31mdhd_pktfwd_lut_lkup: dhd_pktfwd_lut_lkup: pool 1 and unit 15 mismatched
Jan 17 14:40:18 kernel: ^[[0m
Jan 17 14:40:18 kernel: ^[[0;31mdhd_pktfwd_lut_lkup: dhd_pktfwd_lut_lkup: pool 1 and unit 15 mismatched
Jan 17 14:40:18 kernel: ^[[0m
Jan 17 14:40:18 kernel: ^[[0;31mdhd_pktfwd_lut_lkup: dhd_pktfwd_lut_lkup: pool 1 and unit 15 mismatched
Jan 17 14:40:18 kernel: ^[[0m
Jan 17 14:40:18 kernel: ^[[0;31mdhd_pktfwd_lut_lkup: dhd_pktfwd_lut_lkup: pool 1 and unit 15 mismatched
Jan 17 14:40:18 kernel: ^[[0m

the AI mesh nodes will be offline about half the time. Sometimes they get up but even a wired connection to a AIMesh node almost doens'mt connect anymore to my external internet (and it's SLOOOW)

 

[peltco]

I did a factory reset, downgraded my system to 102_2 and rebuild my AI Mesh network. Devices seemed to be connected to my ai mesh nodes.

The AI Mesh nodes RT-AX92U and running on stock firmware 3.0.0.4.388_23695-g0bf7613.
After upgrading again to 102_3 i get the above errors again in my log and disconnects or no clients on my AI Mesh nodes

 

[Ryu Connor]

64 character hex passwords are truncated by the WPA password field, preventing clients from connecting.

Using a smaller password length, like 32 characters, fixes the problem, but the problem isn't supposed to exist to begin with. The AC88U my BE88U just replaced handled 64 character hex passwords without error.

 

[visortgw]

64 character hex passwords are truncated by the WPA password field, preventing clients from connecting.

Using a smaller password length, like 32 characters, fixes the problem, but the problem isn't supposed to exist to begin with. The AC88U my BE88U just replaced handled 64 character hex passwords without error.

The WPA standard is between 8 and 63 characters — try 63 characters.

 

[Ryu Connor]

The WPA standard is between 8 and 63 characters — try 63 characters.

Nay.

This key may be entered either as a string of 64 hexadecimal digits, or as a passphrase of 8 to 63 printable ASCII characters.

This is why the AC88U and my AX6000 can handle 64 character HEX passwords, because that is the standard.

The standard is only a max of 63 with ASCII passwords.

Edit1: That said, I'm thinking that if I set the password via SSH, it will bypass the bug.

Edit2: Linux client connects fine with 64 hex password regardless if set by SSH or WebUI.
iPhone iOS 18.2.1 meanwhile falls apart when using 64 hex password on the BE88U (set by SSH or Web), but works without issue on the AC88U.
No clue if this is iOS problem, AsusWRT, or both problem.