Asuswrt Merlin 3006.102.3 Alpha1 for GT-BE98 Pro

[ExtremeFiretop]

Thanks, that appears to be what I'm seeing (as well as explains what @ExtremeFiretop sees)! I wasn't following this RT-BE86U thread.

My WebGUI glicth still seems related to the AiMesh nodes still; The Wireless page has had issues in the past that I've reported here: https://www.snbforums.com/threads/a...vailable-for-wifi-7-devices.92745/post-933324 and also seen others report before such as here: https://www.snbforums.com/threads/a...vailable-for-wifi-7-devices.92745/post-933251
Basically the same issue, as soon as I turn off the AiMesh nodes the problem goes away:

As soon as i reconnect the nodes, the page goes back to blank other than Smart Connect, previously it appeared disabled, now it appears enabled.
The actual errors in the F12 menu have changed compared to my previous reported link above though;

Uncaught TypeError: Cannot read properties of undefined (reading 'count')
    at asus.js:971:17
    at asus.js:982:3
Advanced_Wireless_Content.asp:1644  Uncaught TypeError: Cannot destructure property 'currentLang' of 'language' as it is undefined.
    at generateControlChannel (Advanced_Wireless_Content.asp:1644:7)
    at generateMainField (Advanced_Wireless_Content.asp:277:9)
    at HTMLDocument.<anonymous> (Advanced_Wireless_Content.asp:80:1)
notification.js:819  Uncaught SyntaxError: Unexpected identifier 'notification'
state.js:1492  Uncaught ReferenceError: notification is not defined
    at notification_script.onload (state.js:1492:1)

I could reset my primary and see if it helps; it's been setup the same since day one with split SSIDs with the first firmware release.

 

[visortgw]

Actually, about Smart Connect - I don't have such setting in my UniFi control panel either. It's done exactly as RMerlin describes the new Asuswrt way - you start with an SSID and attach it to a radio. Multiple radios used enable automatically what Asus calls Smart Connect.



This is again similar to what I see in UniFi. You first define a Network with all the properties, then define an SSID and attach it to a Network, then tell the AP how many radios will broadcast this SSID. This is the common logic of doing things on business systems. When I first run a Pro router got a bit confused how Asus made the things backwards. It was inherited by the old flat network design. Now they are fixing it the way it should be.

Makes logical sense. It just came unexpectedly after using the legacy interface for so long...

 

[Tech9]

I haven't seen the new UI yet, but I like the changes as description. Regular SNB Forum members just need to see it once. The challenge for Asus is to make it user friendly enough for average home users, I guess. SDNs can extend features way further, but the product departs from the consumer market.

 

[ExtremeFiretop]

My WebGUI glicth still seems related to the AiMesh nodes still; The Wireless page has had issues in the past that I've reported here: https://www.snbforums.com/threads/a...vailable-for-wifi-7-devices.92745/post-933324 and also seen others report before such as here: https://www.snbforums.com/threads/a...vailable-for-wifi-7-devices.92745/post-933251
Basically the same issue, as soon as I turn off the AiMesh nodes the problem goes away:

View attachment 62986

View attachment 62984

As soon as i reconnect the nodes, the page goes back to blank other than Smart Connect, previously it appeared disabled, now it appears enabled.
The actual errors in the F12 menu have changed compared to my previous reported link above though;

View attachment 62985

Uncaught TypeError: Cannot read properties of undefined (reading 'count')
    at asus.js:971:17
    at asus.js:982:3
Advanced_Wireless_Content.asp:1644  Uncaught TypeError: Cannot destructure property 'currentLang' of 'language' as it is undefined.
    at generateControlChannel (Advanced_Wireless_Content.asp:1644:7)
    at generateMainField (Advanced_Wireless_Content.asp:277:9)
    at HTMLDocument.<anonymous> (Advanced_Wireless_Content.asp:80:1)
notification.js:819  Uncaught SyntaxError: Unexpected identifier 'notification'
state.js:1492  Uncaught ReferenceError: notification is not defined
    at notification_script.onload (state.js:1492:1)

I could reset my primary and see if it helps; it's been setup the same since day one with split SSIDs with the first firmware release.

I've removed the Gnuton node from the pair, and the issue went away again.
Now it's displaying normally, and I still have the GT-AXE11000 paired and connected to the primary.

I'd say something between the Gnuton node and Merlin primary when using AiMesh.

 

[Tech9]

I've removed the Gnuton node from the pair, and the issue went away again.

The issue can be related to this notice coming with new Asuswrt firmware versions:

"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 suggest resetting the AiMesh router to its default settings and re-establishing the mesh connection."

GNUton firmware for End-of-Life RT-AX92U can't have the latest AiMesh changes. It was built on whatever GPL was last available for it.

 

[ExtremeFiretop]

The issue can be related to this notice coming with new Asuswrt firmware versions:

"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 suggest resetting the AiMesh router to its default settings and re-establishing the mesh connection."

GNUton firmware for End-of-Life RT-AX92U can't have the latest AiMesh changes. It was built on whatever GPL was last available for it.

It's extremely possible; infact it's likely it's related; it's simply too bad ASUS couldn't be more clear on any GPL incompatibilities.
(Specifically between which GPLs and the expected issues) Would of been a nice addition outside of focusing on not downgrading the firmware. I wonder if this has been confirmed at all elsewhere in the forums?

For now; I've changed my configuration so only the GT-AXE11000 is setup as a test node, and instead the Gnuton router is now a stand-alone router I can continue to use for Gnuton firmware testing.

 

[Tech9]

it's simply too bad ASUS couldn't be more clear on any GPL incompatibilities

Agree. The entire AiMesh compatibility thing has to be documented at some point and not just "AiMesh compatible" with users wondering after purchase what and why is or isn't working. This marketing first approach has to change.

 

[RMerlin]

It appears that the VPN Director config settings are there. It's just a browser or web UI issue.

If I close browser (Firefox), reopen the web GUI, select the VPN / VPN Director pulldown menu provided by one of the 3rd-party add-ons (possibly amtm?), then the fully populated VPN Director display is shown. If I then select the VPN Director tab, the empty page is shown. The other VPN page tabs work normally.

That addon breaks every time there's a new firmware that changes anything at the webui level. Don't use it.

VPNDirector page loads fine for me.

 

[Tech9]

pulldown menu provided by one of the 3rd-party add-ons (possibly amtm?)

scMerlin

 

[visortgw]

scMerlin

Thanks. I just found that as well.

 

[visortgw]

That addon breaks every time there's a new firmware that changes anything at the webui level. Don't use it.

VPNDirector page loads fine for me.

Thanks, @RMerlin. Uninstalling scMerlin and clearing browser cache resolved the issue.

 

[matthew_eli]

Actually, I use the 2.5 Gbps WAN/LAN port for WAN so that I have two 10 Gbps ports available to connect to 10 Gbps capable switches!

Ok, but I guess you don't have to specify any VLAN tag for your WAN connection, otherwise you'd be forced to use the 10 Gbit port

 

[visortgw]

My syslog is being flooded with the following messages. Might anyone know the root cause? Thanks.

Dec 17 10:24:37 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[2042] match fails entry.dstid[250]
Dec 17 10:24:41 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[381] match fails entry.dstid[509]
Dec 17 10:24:41 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[381] match fails entry.dstid[509]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:45 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[516] match fails entry.dstid[644]

 

[ExtremeFiretop]

My syslog is being flooded with the following messages. Might anyone know the root cause? Thanks.

Dec 17 10:24:37 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[2042] match fails entry.dstid[250]
Dec 17 10:24:41 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[381] match fails entry.dstid[509]
Dec 17 10:24:41 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[381] match fails entry.dstid[509]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:44 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[515] match fails entry.dstid[643]
Dec 17 10:24:45 S1Rs-GT-BE98_Pro kernel: blog_get_dstentry_by_id:dstid[516] match fails entry.dstid[644]

I can confirm I do not have such flooding.

 

[Blacklistedcard]

I can confirm I do not have such flooding.

Same here I don't see that logging on my BE98 Pro.

 

[RMerlin]

That message shows in dmesg and not in syslog. Same messages are also present with stock firmware 102_37094.

 

[visortgw]

That message shows in dmesg and not in syslog. Same messages are also present with stock firmware 102_37094.

Thanks, @RMerlin. I have filtered out the message using scribe (aka syslog-ng). If I had to guess, it has something to do with Asus' Daylight Savings Time (aka DST) database. Closed source code, I'm assuming?

 

[RMerlin]

Thanks, @RMerlin. I have filtered out the message using scribe (aka syslog-ng). If I had to guess, it has something to do with Asus' Daylight Savings Time (aka DST) database. Closed source code, I'm assuming?

No, this has nothing to do with timezone. It's related to networking, and is used by Broadcom to extend data structures of packets at the kernel level to append private information that they use, probably related to their NAT acceleration or other BCM networking features.

EDIT: The odd thing is that this message should only be visible when logging with a DEBUG level. If you do have everything logged to an external syslog, then that would explain why you get these debug messages. You should adjust logging to not log messages with a DEBUG priority.

 

[visortgw]

No, this has nothing to do with timezone. It's related to networking, and is used by Broadcom to extend data structures of packets at the kernel level to append private information that they use, probably related to their NAT acceleration or other BCM networking features.

EDIT: The odd thing is that this message should only be visible when logging with a DEBUG level. If you do have everything logged to an external syslog, then that would explain why you get these debug messages. You should adjust logging to not log messages with a DEBUG priority.

I uninstalled scribe, and I adjusted logging level. FIXED! Thanks again.