What's new

New models to be introduced with 3006.102.2

  • 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!

3006 is largely 3004 but with SDN, which is highly complex and is spread throughout the whole code base. Everything has to be adapted to deal with that, not just guest networks.

Seems like a crazy idea. I would have thought they would have built SDN on the existing Guest Network framework. Seems like a simpler transition to me but maybe I am not grasping all the features of SDN.
 
Seems like a crazy idea. I would have thought they would have built SDN on the existing Guest Network framework. Seems like a simpler transition to me but maybe I am not grasping all the features of SDN.
SDN is far more complex than justs a guest network. SDN involves the ability to have multiple DNS servers and multiple DoT resolvers running at the same time, for instance, on potentially different VLANs. It can also have dedicated VPN clients and servers attached to individual SDNs.
 
From what I've found myself over the last few days testing the latest 3006 firmware on my GT-AX6000, the multiple DOT servers which are supposed to be assigned to specific VLANs/Guest Networks only, actually just seem to act as a general pool of DOT DNS resolvers unfortunately.

So while I wanted AdGuard only implemented for a Guest network (hosting mostly iOT devices/similar), and then adding ControlD DOT DNS servers for everything else, in reality everything on both the normal and VLAN guest network just went through the list of DOT servers listed on the WAN page, and picked the fastest resolving one, which just happened to be the AdGuard one added on the guest network.

Removing the AdGuard DOT server from the list on the WAN page (which the guest network setup added itself when enabling AdGuard for it), still left AdGuard itself enabled (I could disable AdGuard from the guest network profile if I wanted) and still sent DNS requests from the normal non guest network through AdGuard, bypassing the DOT servers which were ControlD only.

I'll post that as feedback on the Asus Firmware post on the forums here but yeah, still needs some work to get right.
 
If I have a main router GT-AX6000 running a future Merlin 3006-based firmware and the two other (non-pro) as wired backhaul AIMesh nodes and the AIMesh nodes only run 3004 (stock or Merlin) (AX86U), will the new VLAN features work across my network?
 
Last edited:
If I have a main router GT-AX6000 running a future Merlin 3006-based firmware and the two other (non-pro) as wired backhaul AIMesh nodes and the AIMesh nodes only run 3004 (stock or Merlin) (AX86U), will the new VLAN features work across my network?
I don't think 3006.x Merlin is available for the GT-AX6000, don't remember seeing any plans for same either.
 
If I have a main router GT-AX6000 running a future Merlin 3006-based firmware
Are you sure you are running Asus-Merlin firmware and not the stock Asus 3.0.0.6.102? Currently the GT-AX6000 is not supported by the Asus-Merlin 3006.102.x firmware. Only the RT-BE96U, GT-BE98_PRO, RT-BE88U and RT-BE86U are supported by the Asus-Merlin 3006.102.x firmware. The GNuton fork of Asus-Merlin supports the GT-BE98. Currently Asus-Merlin lists the GT-AX6000 at 3004.388.8_2.
 
SDN is far more complex than justs a guest network. SDN involves the ability to have multiple DNS servers and multiple DoT resolvers running at the same time, for instance, on potentially different VLANs. It can also have dedicated VPN clients and servers attached to individual SDNs.

And this is why Asus calls it a Self-Defined-Network not a Software-Defined-Network because anything they do will be less then any actual half decent Software-Defined-Network.
 
Are you sure you are running Asus-Merlin firmware and not the stock Asus 3.0.0.6.102? Currently the GT-AX6000 is not supported by the Asus-Merlin 3006.102.x firmware. Only the RT-BE96U, GT-BE98_PRO, RT-BE88U and RT-BE86U are supported by the Asus-Merlin 3006.102.x firmware. The GNuton fork of Asus-Merlin supports the GT-BE98. Currently Asus-Merlin lists the GT-AX6000 at 3004.388.8_2.
So Merlin has released, but no sign of anything GNUTON for BE98 in terms of test release or final release. Last update was August. I am on stock at the moment and desperate as GNUTON's last update does not apply to v2 hardware if stock firmware was up to date.
 
I'm extremely happy with the current state of the AXE16000. I'm in no rush to shift to 3006. Was really on the fence when I purchased the AXE16000 to replace an AX88 (now in mesh), but it was on sale and it had 2Gb of memory and speedier ethernet connections, so I went for it. It is doing a fantastic job.
Me too!!
 
Hi,

Two new models will make their official Asuswrt-Merlin debut with 3006.102.2: the RT-BE88U and RT-BE86U.

View attachment 61377
View attachment 61378

There is no ETA as to the availability, as development isn't complete yet. The RT-BE88U development is currently based off an old 102_33xxx codebase, and the RT-BE86U is based off the 102_36xxx codebase, with a number of changes in this release that haven't been properly integrated into Asuswrt-Merlin yet.

I am hoping to get updated GPLs in the coming weeks, with no firm ETA at this time, hence I have no idea when firmware releases will be available for these, sorry.
Do you have any news on any of the older models moving to this branch? I mainly mean the "PRO" versions, and any other model that might make the cut? Sorry, I know you have probably been asked this to the gills, I am just curious if you have heard anything new being that is now november.
 
Do you have any news on any of the older models moving to this branch? I mainly mean the "PRO" versions, and any other model that might make the cut? Sorry, I know you have probably been asked this to the gills, I am just curious if you have heard anything new being that is now november.
No.
 
I just recently switched over to stock firmware on my RT-AX86u Pro as it appeared (to me) that it wasn't going to happen anytime soon.
At first I had tried to get everything working (All devices have static IPs and custom Icons), VPN excemptions, etc. working in the previous stock
firmware but could not get the VPN exceptions working correctly...However once they updated my model to
ASUS RT-AX86U_PRO_3.0.0.6_102_34319 firmware I tried again and was successful...Has been running fine now for serveral weeks on
ASUS RT-AX86U_PRO_3.0.0.6_102_34319. Yeah it's not nearly as nice as the Merlin firmware but I could get everything working with the
new firmware. If ASUS ever give's Merlin the firmware Blobs necessary for 3006 code on the Pro models I'll revert back to Merlin.
(But I'm not holding my breath).
 
Doesn't sound good to me.. Maybe it's time to find another router maybe?
Why? I don't have any update ETA for the existing 3006 models either.
 
Well, the ASUS is sending a really huge number of FW updates to routers in the meantime with patches for AICloud security holes.

Looks like they've been reading our forum... :D
 
[Please moderators remove if off-topic]
Does anyone know if the 'ROG' line of routers would offer any benefit (speed/quality of build/security...) to a non-gamer, as compared to non 'ROG' branded routers?
As pace of FW upgrades (and pricing policies) are distinct, I am just curious to find out whether that is down to measurable advantage, or that is plain marketing.
 

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