Beta Asuswrt-Merlin 3006.102.1 Beta is now available for WIfi 7 devices

[baller54]

Thanks. I'll probably upload test builds within 30-60 mins with a different method of matching IP and hostname with a device, but I want to see if based on your info I can confirm if this adjusted method would work.

Happy to test!

 

[RMerlin]

@GHammer Please test the builds inside the Wireless Log Parsing directory:

OneDrive

www.asuswrt-merlin.net

Instead of trying to locate a lease by the MAC, it will now try to locate it by the IP, and only if the iP is not present in the ARP cache then it will fallback to the former MAC-based matching.

 

[GHammer]

@GHammer Please test the builds inside the Wireless Log Parsing directory:

OneDrive

www.asuswrt-merlin.net

Instead of trying to locate a lease by the MAC, it will now try to locate it by the IP, and only if the iP is not present in the ARP cache then it will fallback to the former MAC-based matching.

First, the file inside that directory was named exactly as the last test. I downloaded and installed anyway.

Nothing changed.

Let me say that any device that has a static assignment is always ok in both the client list and the wireless log.

Devices that don't have a static assignment are subject to the MAC being one number different in the wireless log.

Here's the pixel and a TP-Link smart plug as examples.
Additionally, there is an odd entry in the system log, one I've never seen. Attached as be96-syslog.txt

 

[RMerlin]

Devices that don't have a static assignment are subject to the MAC being one number different in the wireless log.

The MAC being different is something done by the Pixel 8, where it uses a different MAC for the DHCP lease versus the wifi association. Nothing I can do about that, it's apparently simply how the Pixel 8 works. What only matters to me is for the Wireless Log to be able to associate the IP and hostname together, which seems fine in your capture - there is no "Unknown" names being shown.

 

[GHammer]

The MAC being different is something done by the Pixel 8, where it uses a different MAC for the DHCP lease versus the wifi association. Nothing I can do about that, it's apparently simply how the Pixel 8 works. What only matters to me is for the Wireless Log to be able to associate the IP and hostname together, which seems fine in your capture - there is no "Unknown" names being shown.

What do you know, working on the test build.
I was away for awhile and just got back.
It took maybe 4-5 minutes after it connected to WiFi, but while I was on the page, the ID apperaed.

 

[GHammer]

What are the kernel: Failed delete entry fe80:0000:0000:0000:b457:c8ff:feb5:3415 ^M messages about?

 

[RMerlin]

It took maybe 4-5 minutes after it connected to WiFi, but while I was on the page, the ID apperaed.

Yes definitely some oddities specific to the Pixel-8 and/or MLO capable clients. The latest changes I've made might help in some scenarios, but I can't make it 100% reliable.

Since that test build I have removed the <unknown> labels that were used in such cases, so it will look less like an error stituation and more like the client list is simply unable to provide the IP and/or hostname of affected clients.

What are the kernel: Failed delete entry fe80:0000:0000:0000:b457:c8ff:feb5:3415 ^M messages about?

No idea. Sounds like debug info left in there by either Broadcom or Asus. There's a higher volume of debug output than usual in these GPLs, probably because Asus are still debugging changes specific to Wifi 7.

 

[GHammer]

Yes definitely some oddities specific to the Pixel-8 and/or MLO capable clients.

There's a disconnect between the network list client map and the wireless log

See my previous example. The Pixel shows no connection info in the client list while that info was in the log entry.

Not a huge thing to me, I don't have strange or unknown devices connect to my network.

Thanks for the IP lookup fix!

 

[RMerlin]

There's a disconnect between the network list client map and the wireless log

As I said before, they are two totally different things. The Wireless Log specifically lists MAC addresses associated with each wireless radios, while the Client List lists clients by their presence on the network. The MACs of your Pixel 8 don't match because the Pixel 8 uses different MACs for DHCP queries and for wireless association.

 

[JDB]

I understand the reasons why but it’s a shame you’re not supporting the GT98 directly.

I’m sure Gnuton does a good job but based on 3004.388.7 it’s looking like their version releases substantially later then yours does

I agree. The entire European market (and probably others!) relies on the non Pro version.

Much as I appreciate Gnuton’s work, does he have the staying power of RMerlin?
Do I want to run my router on a fork that may disappear in 12 months time?

I can’t even find Gnuton’s version to try if I wanted to, which further backs up the above statements. The Merlin firmware has a proper release/update framework behind it meaning I can always find the latest version and its release notes without fishing in Github.

If the BE98 was directly supported I’d have already purchased 4 of them, rebuilt my AiMesh and be running this beta, supporting the cause with feedback.

If it’s just a case of needing a sample, I’ll happily buy a 5th and ship it to you @RMerlin

I’m also happy to DDOS Asus with requests to support you with the GPL. Maybe all European users could join this effort if that is the blocker.

 

[RMerlin]

I can’t even find Gnuton’s version to try if I wanted to

That would be because it's not available yet.

If it’s just a case of needing a sample, I’ll happily buy a 5th and ship it to you @RMerlin

1) That device would be illegal in Canada, and most likely would be seized at the border. That is why Asus and I jointly decided that I would support the GT-BE98_PRO, while Gnuton would support the GT-BE98.
2) I cannot support every single model on my own. Gnuton has been supporting multiple models for many years by now. If you don't like that, then sorry - that's just the way it is. I have a finite amount of time I can devote to this project.

 

[JDB]

That would be because it's not available yet.


1) That device would be illegal in Canada, and most likely would be seized at the border. That is why Asus and I jointly decided that I would support the GT-BE98_PRO, while Gnuton would support the GT-BE98.
2) I cannot support every single model on my own. Gnuton has been supporting multiple models for many years by now. If you don't like that, then sorry - that's just the way it is. I have a finite amount of time I can devote to this project.

With the difference in worldwide frequencies being allowed I feel like many WiFi7 models are going to have this same split.

I appreciate what you are saying about legality and time. But test devices are used all over the world and don’t cause a problem (and from personal experience can say they are not seized! I work in this industry).

If you are confident in Gnuton and my view of WiFi7 models comes true, maybe you can collaborate more closely with him and have some of his releases that extend support into Europe managed under your framework, so users can enjoy a more seamless and closer to OEM experience?

 

[RMerlin]

maybe you can collaborate more closely with him and have some of his releases that extend support into Europe managed under your framework

Gnuton is already forked from my code. While I do the primary code merge + development, he gets his model-specific GPLs from Asus, and handles the merge of these model's binary blobs himself. He handles development and distribution for his models, as the point there is for me not to have to devote any of my own time to these models.

 

[JDB]

Gnuton is already forked from my code. While I do the primary code merge + development, he gets his model-specific GPLs from Asus, and handles the merge of these model's binary blobs himself. He handles development and distribution for his models, as the point there is for me not to have to devote any of my own time to these models.

I get it, it’s your time, and so rightly your way or the highway. And I also know how Gnuton already works with you and ASUS.

I just thought that for the good of an entire continent he might be able to push his released blobs to a new folder on your infrastructure. This could be entirely automated with zero of your time needed long term, just initial setup of his release folder and access rights.

 

[amplatfus]

Hi,

Please, in Guest Network Pro VLAN we can add the LAN ports too?

Thanks,
amplatfus

 

[RMerlin]

Hi,

Please, in Guest Network Pro VLAN we can add the LAN ports too?

Thanks,
amplatfus

Already possible. Define the port VLAN on the Vlan settings page, then create a new Guest Network using the same VLAN.

 

[amplatfus]

Already possible. Define the port VLAN on the Vlan settings page, then create a new Guest Network using the same VLAN.

Thank you very much for reply.
On my old AX88U I didn't find this option yet.
Please, it will be possible on this model too?

Kind regards,
amplatfus

 

[bennor]

On my old AX88U I didn't find this option yet.
Please, it will be possible on this model too?

You won't find the option on an RT-AX88U because that model doesn't support 3006.x firmware which Guest Network Pro is a part of.

Further note what is indicated in the very first post of the thread topic by RMerlin:

Do not ask about support for other models. 3006.102.1 will only support these two models (plus the GT-BE98 by Gnuton), and we will re-evaluate things after that realease is finalized on any other potential device to support. These must be picked in collaboration with Asus as GPL code and device samples (in the case of new devices) are necessary for each individual model.

PS: More on Guest Network Pro at the following link from Asus Support, including a listing routers (doesn't include the RT-AX88U) that support it via the stock Asus 3006.x firmware:

Offizieller Support | ASUS Deutschland

Das ASUS Support Center hilft Ihnen Treiber, Handbücher und Firmware-Versionen herunter zu laden. Hier finden Sie auch FAQs und Troubleshooting Hilfen

www.asus.com

Guest network pro supported models: (more models are coming)
GT-AX11000 Pro
GT-AX6000
GT-AXE16000
GT-BE98 Pro
GT-BE98
GT-BE25000
GT-BE96
GT-BE19000
ZenWiFi Pro ET12
ZenWIFI Pro XT12
RT-AX86U Pro
RT-AX88U Pro
RT-BE96U
RT-BE88U

 

[GHammer]

Back to the Pixel and the differing MACs.
I just setup my old AX86U as a router.
Connected my Pixel.
MACs are the same in both the client list and the wireless log.

So, I'm confused now.

 

[jksmurf]

You won't find the option on an RT-AX88U because that model doesn't support 3006.x firmware which Guest Network Pro is a part of.

Further note what is indicated in the very first post of the thread topic by RMerlin:

PS: More on Guest Network Pro at the following link from Asus Support, including a listing routers (doesn't include the RT-AX88U) that support it via the stock Asus 3006.x firmware:

Offizieller Support | ASUS Deutschland

Das ASUS Support Center hilft Ihnen Treiber, Handbücher und Firmware-Versionen herunter zu laden. Hier finden Sie auch FAQs und Troubleshooting Hilfen

www.asus.com

@bennor you have the patience of a saint… if I had a dollar for every time you rolled that response out … maybe just unleash @Tech9, he’s good for a few giggles.