Beta Asuswrt-Merlin 3006.102.5 Beta is now available

[RMerlin]

Code yes but what about the wireless drivers version I believe they are the same in the latest ASUS release and the 3006.102.5 Beta 2 correct?

CC

Version means nothing if patches are applied on top of existing code.

 

[RMerlin]

Conclusion, there is something different in beta's VPN implementation.

Or their server are blacklisting your VPN's IP address, as many websites do for security reasons.

 

[visortgw]

Possible VPN bug in beta.

I use iDrive to backup my computer. It runs everyday. I also have a VPN running on my Asus GT-AX6000. Everything was running fine on 3006.102.4

Loaded beta 2 yesterday.

This morning, received a failure notice from the automated daily idrive backup. idrive log showed:

"Possible reasons: 1. Ensure that you do not have an intermittent Internet connection. 2. Check if you have granted the necessary privileges on local firewall settings for it to run correctly."

Opened idrive app to try a manual backup.
Received an error message

"Unable to connect to server, Reason: sendfailure"

Here is a screenshot.

View attachment 66917

Looked on Asus router's log...nothing added.

Shutoff VPN for my computer (using VPN Director and a rule setting my computer to WAN). I was able to run idrive app and do a manual backup.

Loaded 3006.102.4 and everything was back to normal.

Conclusion, there is something different in beta's VPN implementation.

Will be addressed in next iteration per @RMerlin:

Beta - Asuswrt-Merlin 3006.102.5 Beta is now available

Directly after a fresh boot: I've seen something similar happen once a few weeks ago during testing but I have been unable to reproduce it since then. As verbose mode indicate tho these are not duplicate, they are different rules. I suspect it's a timing issue when configuring firewall rules...

www.snbforums.com

 

[JohnD5000]

Or their server are blacklisting your VPN's IP address, as many websites do for security reasons.

Why would it work with the same VPN on 3006.102.4 but not 3006.102.5 beta2?

 

[JohnD5000]

Will be addressed in next iteration per @RMerlin:

Beta - Asuswrt-Merlin 3006.102.5 Beta is now available

Directly after a fresh boot: I've seen something similar happen once a few weeks ago during testing but I have been unable to reproduce it since then. As verbose mode indicate tho these are not duplicate, they are different rules. I suspect it's a timing issue when configuring firewall rules...

www.snbforums.com

Thanks, I'll retry with the next iteration to see if it is fixed.

 

[JohnD5000]

Will be addressed in next iteration per @RMerlin:

Beta - Asuswrt-Merlin 3006.102.5 Beta is now available

Directly after a fresh boot: I've seen something similar happen once a few weeks ago during testing but I have been unable to reproduce it since then. As verbose mode indicate tho these are not duplicate, they are different rules. I suspect it's a timing issue when configuring firewall rules...

www.snbforums.com

I just reread that. It says OpenVPN. My VPN is setup with Wireguard

 

[bacon612]

Channel 0 usually indicates either the radio is crashed, or the settings are corrupted. Try first to do a complete power cycle of the router do reset the hardware. If it still fails, next step is to do a factory default reset and manually reconfigure it.

After that if it still shows channel 0 then you probably need to RMA the router.

Did a factory reset. Seems that the 5GHz radio is shot as it still isnt working. RMA here we come.

 

[Ripshod]

Conclusion, there is something different in beta's VPN implementation

I see nothing wrong with my client running Nord over Wireguard.
Yes, I run VPNMON-R3 (unofficial alpha), but that hasn't registered any downtime.

 

[robinjoo1]

are these messages normal i get the from time to time


Jul 24 19:17:51 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:52 wlceventd: wlceventd_proc_event(685): eth6: Auth 58:B6:23:81:87:8B, status: Successful (0), rssi:-39
Jul 24 19:17:52 wlceventd: wlceventd_proc_event(722): eth6: Assoc 58:B6:23:81:87:8B, status: Successful (0), rssi:-39
Jul 24 19:17:52 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:52 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:53 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:54 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:54 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:55 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:55 miniupnpd[710774]: shutting down MiniUPnPd
Jul 24 19:17:55 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:56 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:56 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:57 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:57 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:58 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:59 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:17:59 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:00 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:00 miniupnpd[711964]: HTTP listening on port 42331
Jul 24 19:18:00 miniupnpd[711964]: no HTTP IPv6 address, disabling IPv6
Jul 24 19:18:00 miniupnpd[711964]: Listening for NAT-PMP/PCP traffic on port 5351
Jul 24 19:18:00 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:01 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:01 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:02 kernel: Serdes 8 False Link Up with Error Symbol 0xf4 at 3.c466h at speed 2500Mbps
Jul 24 19:18:02 kernel: ^[[0;30;103mWarning: Serdes at 8 link does not go up following external copper PHY at 21.^[[0m
Jul 24 19:18:03 kernel: ^[[0;34m[NTC xport] xport_init: rc = 0; intf = 5 port = 4 spd = 2.5G dup = 1
Jul 24 19:18:03 kernel: ^[[0m

 

[cc666]

Version means nothing if patches are applied on top of existing code.

Eric

Are the wireless drivers the same on FW_GT_BE98_PRO_3006_10237839 vs GT-BE98_PRO_3006_102.5_beta2?

wl0: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl1: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl2: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl3: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13

CC

 

[RMerlin]

Eric

Are the wireless drivers the same on FW_GT_BE98_PRO_3006_10237839 vs GT-BE98_PRO_3006_102.5_beta2?

wl0: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl1: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl2: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13
wl3: Jun 24 2025 15:53:28 version 17.10.369.39012 (r839077) BSPv1W13

CC

I have no idea what's in the release firmware. As I said, the verison number doesn't indicate what patches were applied on it. All I can tell you is that the Broadcom patch you are referring to is also present in the driver that I am using.

 

[RMerlin]

Why would it work with the same VPN on 3006.102.4 but not 3006.102.5 beta2?

I don't know. Could be connecting to a different server between reboots. All I can say is that the Wireguard code hasn't changed in ages, and it's also working fine for me. If only iDrive is having issues, then they must be doing something with traffic coming from your VPN provider.

 

[clvk07]

Updated from 102.3 (Be88u, plus be86u as mesh) and after 15 minutes all wireless clients disconnected. Rebooted, worked and then again after 20 minutes all disconnection. Wouldnt connect anymore. Not sure if the same issue, but had an issue with previuos firmwares where when I modified TX power transmission down to balanced or lower all wireless clients would not connect. Sample log, goes on forever.... Flashed back to 102.3 all good.

Jul 23 20:03:15 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:15 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0
Jul 23 20:03:15 Asus-6E897DC-C hostapd wl0.2: STA d8:f1:5b:e0:f3:ad IEEE 802.11: disassociated
Jul 23 20:03:15 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:18 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0
Jul 23 20:03:18 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:18 Asus-6E897DC-C hostapd wl0.2: STA d8:f1:5b:e0:f3:ad IEEE 802.11: disassociated
Jul 23 20:03:18 Asus-6E897DC-C hostapd wl0.2: STA d8:f1:5b:e0:f3:ad IEEE 802.11: disassociated
Jul 23 20:03:18 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0
Jul 23 20:03:18 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:21 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0
Jul 23 20:03:21 Asus-6E897DC-C hostapd wl0.2: STA d8:f1:5b:e0:f3:ad IEEE 802.11: disassociated
Jul 23 20:03:21 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:24 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0
Jul 23 20:03:24 Asus-6E897DC-C hostapd wl0.2: STA d8:f1:5b:e0:f3:ad IEEE 802.11: disassociated
Jul 23 20:03:24 Asus-6E897DC-C wlceventd wlceventd_proc_event(685): wl0.2: Auth D8:F1:5B:E0:F3:AD, status: Successful (0), rssi:0
Jul 23 20:03:24 Asus-6E897DC-C wlceventd wlceventd_proc_event(645): wl0.2: Deauth_ind D8:F1:5B:E0:F3:AD, status: 0, reason: Unspecified reason (1), rssi:0

 

[RMerlin]

Updated from 102.3 (Be88u, plus be86u as mesh) and after 15 minutes all wireless clients disconnected. Rebooted, worked and then again after 20 minutes all disconnection. Wouldnt connect anymore. Not sure if the same issue, but had an issue with previuos firmwares where when I modified TX power transmission down to balanced or lower all wireless clients would not connect. Sample log, goes on forever.... Flashed back to 102.3 all good.

Reset your nodes.

 

[Lax]

There seems to be an issue with the reported clients count as in the attached snapshot... it keeps increasing. However, if exported it contains less nodes(93) which is correct. Also ASUS mobile app shows correct number (93) of clients.
There is another issue with the iPhone clients with the "limit IP tracking" option. Had to disable this to get the IOS devices working. No isuch ssues with the ASUS firmware.

 

[visortgw]

There seems to be an issue with the reported clients count as in the attached snapshot... it keeps increasing. However, if exported it contains less nodes(93) which is correct. Also ASUS mobile app shows correct number (93) of clients.
There is another issue with the iPhone clients with the "limit IP tracking" option. Had to disable this to get the IOS devices working. No isuch ssues with the ASUS firmware.

Previously reported. It seems to "settle" to normalcy over time.

 

[bluepoint]

There is another issue with the iPhone clients with the "limit IP tracking" option. Had to disable this to get the IOS devices working. No isuch ssues with the ASUS firmware.

"Limit IP tracking" enabled works here with all iOS devices.

 

[chris.at]

I just saw that on the WAN page there is a new VLAN section (sorry if it was there already before with 3006, I just saw it now after installing this beta). Do I interpret this correctly that I could remove the vlan setting from the LAN/IPTV section now and configure it directly on the WAN, where it belongs? I need PPPoE with vlan 31 but don't want to break the internet by moving the vlan from iptv to wan... Anyone already tried this and had success?

 

[Treadler]

There seems to be an issue with the reported clients count as in the attached snapshot... it keeps increasing. However, if exported it contains less nodes(93) which is correct. Also ASUS mobile app shows correct number (93) of clients.
There is another issue with the iPhone clients with the "limit IP tracking" option. Had to disable this to get the IOS devices working. No isuch ssues with the ASUS firmware.

No issues here with idevices. Limit ip addys enabled, all good.