What's new

ANNOUNCEMENT: Asuswrt-Merlin support underway for 3 Wifi 7 routers

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

RMerlin

Asuswrt-Merlin dev
Staff member
Hi everyone,

I am now able to officially announce support for three different Wifi 7 routers is currently under development, to be part of the 3006.102.1 release:

RT-BE96U
GT-BE98_PRO
GT-BE98 (by Gnuton)

1715957668785.png


Things are still too early to have any kind of ETA, even for snapshot builds, as there are a number of things still needing to be done, as this means not only new devices, but also a new technology (Wifi 7) and a new codebase (Asuswrt 3.0.0.6).

As previously indicated in the 3006 discussion thread, I will use the occasion of the move to 3006 to implement a number of changes that might not be 100% backward compatible with 3004 in terms of behaviour or third party addon compatibility. Here are some of the things I have noted down so far (so I don't forget to include them in the future changelog):

Code:
- VPN client tables changed, to integrate into Asus's SDN/Fusion layout.
  /etc/iproute2/rt_tables points to the new tables, so using names is unchanged.

- Due to growing differences between stock and Merlin, going from stock to Merlin
  when anything related to VPNs was already configured should ideally get a factory
  default reset, as SDN indexes won't match.
 (TODO: possibly investigate clearing these two in format.c?)

- NFS not supported on WIfi 7 devices (compatibility issues between nfs-utils
  and the new glibc these devices use)

- Removed option dns_local_cache from Tools -> Tweak settings, to avoid issues with SDN networks
  that run their own dnsmasq instances.

- OpenVPN: merged stop/start toggle with the Start with WAN into a single "Enable client" option,
  to match WireGuard, and also simplify things.  Enabling a client will start it, and it will also
  auto start at WAN up until it gets disabled.

- dnsmasq-INDEX.conf.add, stubby-INDEX.yml.add are appended to SDN config files (INDEX = SDN index value)

- dnsmasq-sdn.postconf and stubby-sdn.postconf are executed, with first argument being the path to
  the config filename for that SDN index, and the second argument is the SDN index number.

- Third party devs: chart.js was upgraded from 2.x to 3.x, which is not backward compatible.

On supported models, Asuswrt-Merlin 3006 will include support for VLAN and Guest Network Pro (SDN). VPN Director will remain Asuswrt-Merlin's method of handling VPN client routing, although Guest Network Pro rules will have a higher priority over VPNDirector rules.

I am also doing some housekeeping in the 3006 branch, such as removing the binary blobs + SDK for WIfi 5 devices, as these will never be supported by 3006 - this will speed things up a bit for us devs by reducing the amount of files to be checked out by git.

For the time being things are still being developed on a private git repo due to frequent git history cleanups. I'm planning on possibly moving the 3006 branch to the public git over the coming days, depending on how things go with the cleanup and reconciliating both repos.

Just to reiterate: don't ask for any ETA on availability, or for support for other models. 3006.102.1 will only support these three models, 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.
 
I am re-evaluating whether or not to continue offering ROG UI variant for the GT models. I haven't touched any of the ROG UI yet for 3006. If I find out I need to do a lot of extra work specifically for the ROG UI, then there's a good chance I might drop its support and only support the regular grey UI.
 
I am re-evaluating whether or not to continue offering ROG UI variant for the GT models. I haven't touched any of the ROG UI yet for 3006. If I find out I need to do a lot of extra work specifically for the ROG UI, then there's a good chance I might drop its support and only support the regular grey UI.
Simplify your life and just stick with one... it's the one we all know and grew up with. In full support of this!
 
3006.102.1 will only support these three models, 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.
This would have been the way to go for 386/388 AC/AX models as well - separate GPLs specific to each model, instead of a common GPL for all of them.
Anyway, better late than never. Thank you!
 
Hi everyone,

I am now able to officially announce support for three different Wifi 7 routers is currently under development, to be part of the 3006.102.1 release:

RT-BE96U
GT-BE98_PRO
GT-BE98 (by Gnuton)

View attachment 58755

Things are still too early to have any kind of ETA, even for snapshot builds, as there are a number of things still needing to be done, as this means not only new devices, but also a new technology (Wifi 7) and a new codebase (Asuswrt 3.0.0.6).

As previously indicated in the 3006 discussion thread, I will use the occasion of the move to 3006 to implement a number of changes that might not be 100% backward compatible with 3004 in terms of behaviour or third party addon compatibility. Here are some of the things I have noted down so far (so I don't forget to include them in the future changelog):

Code:
- VPN client tables changed, to integrate into Asus's SDN/Fusion layout.
  /etc/iproute2/rt_tables points to the new tables, so using names is unchanged.

- Due to growing differences between stock and Merlin, going from stock to Merlin
  when anything related to VPNs was already configured should ideally get a factory
  default reset, as SDN indexes won't match.
 (TODO: possibly investigate clearing these two in format.c?)

- NFS not supported on WIfi 7 devices (compatibility issues between nfs-utils
  and the new glibc these devices use)

- Removed option dns_local_cache from Tools -> Tweak settings, to avoid issues with SDN networks
  that run their own dnsmasq instances.

- OpenVPN: merged stop/start toggle with the Start with WAN into a single "Enable client" option,
  to match WireGuard, and also simplify things.  Enabling a client will start it, and it will also
  auto start at WAN up until it gets disabled.

- dnsmasq-INDEX.conf.add, stubby-INDEX.yml.add are appended to SDN config files (INDEX = SDN index value)

- dnsmasq-sdn.postconf and stubby-sdn.postconf are executed, with first argument being the path to
  the config filename for that SDN index, and the second argument is the SDN index number.

- Third party devs: chart.js was upgraded from 2.x to 3.x, which is not backward compatible.

On supported models, Asuswrt-Merlin 3006 will include support for VLAN and Guest Network Pro (SDN). VPN Director will remain Asuswrt-Merlin's method of handling VPN client routing, although Guest Network Pro rules will have a higher priority over VPNDirector rules.

I am also doing some housekeeping in the 3006 branch, such as removing the binary blobs + SDK for WIfi 5 devices, as these will never be supported by 3006 - this will speed things up a bit for us devs by reducing the amount of files to be checked out by git.

For the time being things are still being developed on a private git repo due to frequent git history cleanups. I'm planning on possibly moving the 3006 branch to the public git over the coming days, depending on how things go with the cleanup and reconciliating both repos.

Just to reiterate: don't ask for any ETA on availability, or for support for other models. 3006.102.1 will only support these three models, 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.
I thought it would support be88u, but based on the current situation, I have to purchase a new device, which will be a significant expense as I need three. I'm really restless
 
Screenshots showing some of the 3006 features.
 

Attachments

  • GNPro1.png
    GNPro1.png
    117.9 KB · Views: 1,199
  • GNPro2.png
    GNPro2.png
    37 KB · Views: 1,179
  • DNSDirector.png
    DNSDirector.png
    129.7 KB · Views: 1,116
  • WirelessLog.png
    WirelessLog.png
    118.7 KB · Views: 1,175
This would have been the way to go for 386/388 AC/AX models as well - separate GPLs specific to each model, instead of a common GPL for all of them.
This has always been the case, each model always had its own separate GPL. It's impossible to share a GPL for more than one model, as each GPL contains precompiled pieces that only work for one specific device.
 
Individual git commits for 3006 as of today:

Code:
merlin@ubuntu-dev:~/amng.3006$ git log --oneline master..3006 | wc -l
166
 
Hi everyone,

I am now able to officially announce support for three different Wifi 7 routers is currently under development, to be part of the 3006.102.1 release:

RT-BE96U
GT-BE98_PRO
GT-BE98 (by Gnuton)

View attachment 58755

Things are still too early to have any kind of ETA, even for snapshot builds, as there are a number of things still needing to be done, as this means not only new devices, but also a new technology (Wifi 7) and a new codebase (Asuswrt 3.0.0.6).

As previously indicated in the 3006 discussion thread, I will use the occasion of the move to 3006 to implement a number of changes that might not be 100% backward compatible with 3004 in terms of behaviour or third party addon compatibility. Here are some of the things I have noted down so far (so I don't forget to include them in the future changelog):

Code:
- VPN client tables changed, to integrate into Asus's SDN/Fusion layout.
  /etc/iproute2/rt_tables points to the new tables, so using names is unchanged.

- Due to growing differences between stock and Merlin, going from stock to Merlin
  when anything related to VPNs was already configured should ideally get a factory
  default reset, as SDN indexes won't match.
 (TODO: possibly investigate clearing these two in format.c?)

- NFS not supported on WIfi 7 devices (compatibility issues between nfs-utils
  and the new glibc these devices use)

- Removed option dns_local_cache from Tools -> Tweak settings, to avoid issues with SDN networks
  that run their own dnsmasq instances.

- OpenVPN: merged stop/start toggle with the Start with WAN into a single "Enable client" option,
  to match WireGuard, and also simplify things.  Enabling a client will start it, and it will also
  auto start at WAN up until it gets disabled.

- dnsmasq-INDEX.conf.add, stubby-INDEX.yml.add are appended to SDN config files (INDEX = SDN index value)

- dnsmasq-sdn.postconf and stubby-sdn.postconf are executed, with first argument being the path to
  the config filename for that SDN index, and the second argument is the SDN index number.

- Third party devs: chart.js was upgraded from 2.x to 3.x, which is not backward compatible.

On supported models, Asuswrt-Merlin 3006 will include support for VLAN and Guest Network Pro (SDN). VPN Director will remain Asuswrt-Merlin's method of handling VPN client routing, although Guest Network Pro rules will have a higher priority over VPNDirector rules.

I am also doing some housekeeping in the 3006 branch, such as removing the binary blobs + SDK for WIfi 5 devices, as these will never be supported by 3006 - this will speed things up a bit for us devs by reducing the amount of files to be checked out by git.

For the time being things are still being developed on a private git repo due to frequent git history cleanups. I'm planning on possibly moving the 3006 branch to the public git over the coming days, depending on how things go with the cleanup and reconciliating both repos.

Just to reiterate: don't ask for any ETA on availability, or for support for other models. 3006.102.1 will only support these three models, 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.
great when the price comes down and I have some 7 clients I might buy one , see it runs 18% cooler , cooler than what ?
 
I am re-evaluating whether or not to continue offering ROG UI variant for the GT models. I haven't touched any of the ROG UI yet for 3006. If I find out I need to do a lot of extra work specifically for the ROG UI, then there's a good chance I might drop its support and only support the regular grey UI.
I just finished to set-up my new GT-AX6000 and wanted to give a go to stock 3006. I find the GUI so hard to focus on and heavy for the eye. It's just my first impression of someone who saw for the 1st time in his life the ROG GUI.
As Viktor said, I think you should stick with the grey UI that we are all used and easy to navigate.
Thank you.
 
Simplify your life and just stick with one... it's the one we all know and grew up with. In full support of this!
+1

Invest your time in more useful things for everyone.
We don't need no flashy ROG theme, we just need the inmense added value your build has, even if it was C64 styled 😁 .
 
Last edited:
So the GT-BE98 builds aren't done by you? I was under the assumption that the BE98 and Pro were essentially the same just that the pro had 2 6GHz bands enabled and the non pro had 2 5GHz bands enabled.
 
I just finished to set-up my new GT-AX6000 and wanted to give a go to stock 3006. I find the GUI so hard to focus on and heavy for the eye. It's just my first impression of someone who saw for the 1st time in his life the ROG GUI.
As Viktor said, I think you should stick with the grey UI that we are all used and easy to navigate.
Thank you.
You're not a Gameur?!
 
I am re-evaluating whether or not to continue offering ROG UI variant for the GT models. I haven't touched any of the ROG UI yet for 3006. If I find out I need to do a lot of extra work specifically for the ROG UI, then there's a good chance I might drop its support and only support the regular grey UI.

You are more than welcome to drop the ROG UI.
 
So the GT-BE98 builds aren't done by you? I was under the assumption that the BE98 and Pro were essentially the same just that the pro had 2 6GHz bands enabled and the non pro had 2 5GHz bands enabled.
The GT-BE98 cannot be sold in North America for regulatory reasons, any shipped device sample might get rejected at the border. That's why Gnuton is taking care of it since he lives in Europe.

MLO planned support ?
First screenshot.
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top