Announcement: 3006 progress report - it's a go

[sfx2000]

Asus does not need me, they already have a number of developers whose programming skills are away ahead of my limited hobbyist-level skills. I'm primarily an IT guy, not a software engineer.

Yes, I know your position there.

Hopefully at least they throw hardware at you to work with.

It's always been my thought that Asus has benefitted big-time because of AsusWRT-RMerlin and SNB Forums...

 

[dlandiss]

It's always been my thought that Asus has benefitted big-time because of AsusWRT-RMerlin and SNB Forums...

I second that.

 

[neil0311]

In fact most never even update firmware on home routers from the time of purchase.

They may have very well been the case several years ago, but I think with auto updating, it’s probably less the case now.

Just keeping security vulnerabilities patched is a big driver for vendors like Asus.

 

[Broken Hope]

When you say guest network pro can have its own DHCP server, are you saying this option will spawn a separate DHCP server if turned off, otherwise just use the system DHCP otherwise?

This is taken from my own GT-BE98

 

[Rajjco]

Any chance to make Guest Network Pro work on devices running in AP Mode?

 

[RMerlin]

When you say guest network pro can have its own DHCP server, are you saying this option will spawn a separate DHCP server if turned off, otherwise just use the system DHCP otherwise?

No, it will spawn another DHCP server if turned on.

Any chance to make Guest Network Pro work on devices running in AP Mode?

No, because an AP has no control over VLANs of the main router, so it would make no sense on an AP.

 

[omrij]

Asus implemented VLAN also in access point mode. So you can use it as smart switch/access point which is VLAN aware.

Beta - Asus GT-AX6000 beta firmware version 9.0.0.6_102_33874 (2024/02/23)

No. This firmware is NOT affected by CVE 2023-50868 and CVE 2023-50387. This has already been explained in this thread. nothing in 9 months that affects it? that'd certainly be good news. sorry didn't read about that earlier. i was assuming they're also closing other bugs / security issues...

www.snbforums.com

 

[Mutzli]

What is the underlying Linux kernel version for this release?

 

[RMerlin]

What is the underlying Linux kernel version for this release?

The kernel is not tied to the firmware version, it's tied to the SDK for a specific model. There are no kernel version changes.

 

[qq3748]

Can't wait for the new firmware!

 

[pirx73]

@RMerlin - if i understood correctly RT-AX68U is off the supported router list for this release?

 

[L&LD]

It was never on it.

End-of-life product list

 

[RMerlin]

Asus implemented support for DNSDirector within SDN (probably they intend to eventually use it for their mobile app support of DNS blocking). I implemented a web interface so Asuswrt-Merlin users can now apply DNSDirecctor to specific Guest Networks (on top of the fact that you currently can specify different DNS servers for each Guest Network - DNSDirector will allow its usual enforcing).

 

[dave14305]

I'm taking the opportunity of this 3004 -> 3006 jump to make some lower level changes that might not be 100% backward compatible. I expect quite a few addons will be broken by it (like those that tie into guest networks or VPN), their developers will need to adjust once 3006 enters public testing. Best to break them all at the same time (as 3006 itself will break a few things), so they will only need fixing once.

- Migrating Chart.js from 2.x to 3.x (sadly, Chart.js breaks all backward compatibility iin these major upgrades). That will require adjusting the generation code for all the charts shown by Classification, TrafficMonitoring and Sysinfo, something I had been postponing for quite some time due to the amount of work involved. It will be necessary if we ever need to support
Asus's dashboard since it uses Chart.js 3.9, and therefore would break any existing charts.

For the addons that do use Chart.js today, will you consider backporting version 3.9.1 to 386_x so that we don't have to support different chart.js versions for different models? Or at least include the new version somewhere in 386_x (e.g. chart-391.min.js), even if you don't want to update your own charts in 386_x?

 

[RMerlin]

For the addons that do use Chart.js today, will you consider backporting version 3.9.1 to 386_x so that we don't have to support different chart.js versions for different models? Or at least include the new version somewhere in 386_x (e.g. chart-391.min.js), even if you don't want to update your own charts in 386_x?

That's something that might be discussed among the community once we get closer to the public beta cycle, whether third party devs prefer to be able to tell which version to support based on the major revision (3004 would be 2.x, 3006 would be 3.x), or if they prefer to only support whichever is newest, and expect 3004 users to update to, say, 3004.388.8, so they share the same version as 3006.

There are a few similar backward compatibility breaking changes in 3006 which we will have to collectively decide if we want to keep them separate, or have them backported to 3004.

 

[violetenergy]

It was never on it.

End-of-life product list

No clear for me for rt-ax86u non pro. I know pro will be supported but standard version don't have statement

 

[L&LD]

As of today, RMerlin has mentioned that the RT-AX86U (orig) will not be getting 3.0.0.6.xxx level firmware. I haven't seen anything to contradict this so far.

 

[Kingp1n]

As of today, RMerlin has mentioned that the RT-AX86U (orig) will not be getting 3.0.0.6.xxx level firmware. I haven't seen anything to contradict this so far.

This would also include GT-AX11000 (non-pro) correct? If so...time to upgrade again haha.

 

[L&LD]

I'm not quite 100% sure about the stated status of that model, but I do believe you're correct.

 

[Ripshod]

If asus don't give certain models 3.0.0.6 I don't see them taking kindly to @RMerlin doing it. I think the same for my RT-AX88U.