Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[HorseCalledHorse]

So, I have a RT-AX88U Pro running 3004.388.8_4
And an Aimesh RT-AC86U running 3004.386.14_2

So, If I update the AX88U Pro to 3006, with AiMesh still work?
I don't use any guest networks.

Very similar setup here, with an RT-AX86U running 3004.388.8_4 and an RT-AC86U as the node. No guest networks either. I haven't tried the 3006 beta yet, but my guess is it will still work fine. Of course if anyone finds otherwise, yell loudly

I also have my router's IP set to http://192.168.0.1/ and I'm wondering if the need to tick off the new ASUS user agreements others have mentioned might complicate access to my router once I upgrade.

 

[visortgw]

Regarding guest network: I'm using network #2 at the moment with 3004 because I don't want the guests on a separate subnet (which is the case with guest #1). Is this still the same with 3006, that guest network #1 would use another ip subnet and therefore #2 should be used in my case? Would be nice if someone could tell me before upgrading to 3006. Thank you in advance.

Fully configurable with Advanced Settings of Guest Network Pro or Nework tab (depending on router model).

 

[TurnstileBlues]

So, I have a RT-AX88U Pro running 3004.388.8_4
And an Aimesh RT-AC86U running 3004.386.14_2

So, If I update the AX88U Pro to 3006, with AiMesh still work?
I don't use any guest networks.

I'm using 86U Pro as my main, with the same aimesh node as you.

Both alphas worked fine for me 86U and this beta also works without any issues.

 

[bennor]

So, If I update the AX88U Pro to 3006, with AiMesh still work?

Yes AiMesh should still work. Note what RMerlin states in the initial post.

Make sure you do read the changelog, especially if migrating from 3004 to 3006. I documented the known recommendations from Asus' own changelog, but there might be further compatibility issues arising when upgrading from 3004. In particular, I would recommend disconnecting and reconnecting any AiMesh node. Also, double check Wireless settings.

 

[Mutzli]

Bussy morning updating all of my routers. So far everything is working as expected.

 

[HeadBanger]

Great to see that the GT-AXE16000 is finally getting this (beta) 3006 release. Flashed this morning and all working fine. Asus have also finally fixed the AiMesh bind bugs in this release (clients would drop off the network completely if bound to any access point) which I never thought would get fixed! I haven't played with the VLAN settings yet - will have a tinker at the weekend.

Thanks as always to RMerlin.

HB

 

[RMerlin]

Would it be possible to display this in the web interface as well?

No..

only accepting 21 of 32 Manual Reservations in my IoT Guest VLAN as documented here, with the trials I carried out.

Your entries are probably too large and there's not enough space in nvram to store them all. Nothing I can do about it.

 

[Jeffrey Young]

Unfortunately one issue remains from the Alpha, I was hoping the beta would fix my issue (and it might be only me as no one else has reported it, but not sure who tried...) of only accepting 21 of 32 Manual Reservations in my IoT Guest VLAN as documented here, with the trials I carried out.

Use one of the new dnsmasq.conf.add scripts for the index of your IoT lan and add your reservations there.

 

[bbunge]

Flashed over Asus firmware. Factory reset and manually configured. Added AiMesh node on the 2.5 G port. IoT Guest WIFI on 2.4 GHz. Enabled DNS Director - router. Disabled 160 MHz and DFS on WIFI. Enabled Wireguard server and Instant Guard.
Set up AMTM, used USB2 thumb drive that had Entware and Diversion from prior test of Merlin firmware, added 2 GB swap, enabled Entware and Diversion (was really pleased that Diversion set up with the prior settings and block list!), installed Skynet.
Noticed that the Guest Network Pro has a slider to enable AdGuard (something new coming to the Asus firmware?)
No issues noted with my configuration or operation so far.

 

[chris.at]

Some wireless settings moved to the professional tab which is fine. The setting "b/g Protection" can now be disabled but after clicking "Save" it's enabled again. Thats what was missing all the time, get rid of this mechanism, but it doesn't store the disabled setting (it stays enabled even when in "n only" and/or "disable 11b" mode). Maybe this could be fixed?

 

[ryosuke]

Just wondering why under wireless general - smart connect for radio bands only allows for tri-band and don't have just 5Ghz? but i am able to set it under network map - wireless

 

[jerry6]

Upgrade from 3006-2.2 all working well , thanks that was quick .
Now looking at the beancounter router the be92u as you have starrted supporting it , if you get to release FW I might buy one to see how much better wifi7 is . AS of now getting close to promised speed on my 1100 pro by wireless 975/98 of a Theoretical 1GB /100 line

 

[GaselK]

IoT devices (2 in 2.4 GHz) (IoT network setup in Guest Network Pro) don't show in IoT tab (0 instead of 2).
In Network Map, View List are in the normal 2.4 GHz group (IoT remains empty), but,
in System Log - Wireless Log they appear correctly in Guest Network table under the proper IoT ssid.
Restarting router IoT devices shows in Guest Network Pro tab but in offtime schedule where they should be offline.

 

[dave14305]

Following up on this issue from the alpha thread:

[ 3006.102_4 alpha Build(s) ] available build(s)

Previously: - Code turning LEDs off is Asus' closed source - Code turning LEDs on was partly mine (per model) and partly Asus's closed source - Code sharing the LED status between AiMesh nodes is closed source...

www.snbforums.com

The ‘x’ is missing in the offline section of the clientlist dropdown throughout the GUI, wherever it is used.

It looks like somewhere in the build process the × character is being removed from client_function.js. It’s in the repo, but not on the router anymore in /www. Therefore, there is nothing to click to remove the offline client entry.

https://github.com/RMerl/asuswrt-merlin.ng/blob/26fcd4ff8800b063a02ddb1009473bef7d23a3ff/release/src/router/www/client_function.js#L3789

Perhaps replace the x with ×

 

[Howard_inGA]

After installing the beta, I noted that the system time is stuck on Mon, Jan 01 00:17:26 2024. Today's date isn't loading after the update.
Additionally, I haven't de/re'ed the airmesh node. It seems to be working 4.0?
Any ideas?
_________________________________________________________________________________________________________________________________________________
To resolve the time problem, I went to the admin/system page. Had to reselect my time zone, then tick DNS QUERY, then verify the dns.msftncsi.com for network monitoring. See help here: https://www.asus.com/support/faq/1037370/
While this selection is in the same block as the LED on/off selection, I TOUCHED NOTHING...AND I'm happy as a clam~!??!;-)

 

[bennor]

Updated a RT-AX86U Pro to the beta. In general, so far everything seems to be working as expected on the router in a basic setup with two Guest Network Pro Customized Networks, each on their own WiFi band. Not using Smart Connect. No AiMesh. Installed YazDHCP develop version (1.0.7) and was able to import the manual DHCP reservations that were used in the prior 3004.x Asus-Merlin firmware.

Have successfully created manual IP reservations for the two Guest Network Pro client networks using /jffs/configs/dnsmasq-1.conf.add (permissions 0644) and /jffs/configs/dnsmasq-2.conf.add (permissions 0644) files. Correct names (from those dnsmasq-x.conf.add files) are correctly populated on the; Network Map, Client Status, Client List, Guest Network Pro client lists, and Wireless log sections. Examples for others (MAC address,IPAddress,ClientName):
/jffs/configs/dnsmasq-1.conf.add

dhcp-host=AA:BB:CC:DD:EE:FF,192.168.52.21,MiniSmartPlug1
dhcp-host=GG:HH:II:JJ:KK:LL,192.168.52.22,MiniSmartPlug2

/jffs/configs/dnsmasq-2.conf.add

dhcp-host=AA:BB:CC:DD:EE:FF,192.168.53.21,WiFiCamera1
dhcp-host=GG:HH:II:JJ:KK:LL,192.168.53.22,WiFiCamera2

I assume one could probably add individual lease time if needed. I didn't try it for my setup.

The DNS Director for Guest Network Pro networks is a nice touch. Can now have Guest Network Pro clients use a local network Pi-Hole IP address for DNS resolving when the Guest Network Pro "Use same subnet as main network" setting is disabled. This was something I couldn't seem to find a way use the local network Pi-Hole under the stock Asus 3006 firmware for the Guest Network Pro clients when having Use same subnet as main network was set to disabled.

To that end however, the local main LAN network Pi-Hole is not correctly resolving the Guest Network Pro client names from the router. Instead I have to use a Host file on the Pi-Hole device (a Raspberry Pi 3B+) to list there manual Guest Network Pro IP reservations along with their name. In the past when using YazFi one could create the /etc/dnsmasq.d/10-subnet-dns.conf file on the Pi-Hole device and use something like the following code (for each YazFi guest network) in that file to have the Pi-Hole resolve the client names when queries were made to the Asus router.

server=/3.168.192.in-addr.arpa/192.168.2.1
server=/4.168.192.in-addr.arpa/192.168.2.1

Tried substituting in the Guest Network Pro IP subnet's (52 and 53 for 3 and 4 respectively) in the code example (rebooted router) but that didn't work.

Any suggestions on getting Pi-Hole to properly query the Asus router for the Guest Network Client names without resorting to using a Hosts file on the Pi-Hole device?

Other then that, no other major issues have been experienced (so far ).

Post updated to fix incorrect file name.

 

[jksmurf]

Your entries are probably too large and there's not enough space in nvram to store them all. Nothing I can do about it.

Oh, that’s disappointing and I fully appreciate you’re not responsible for nvram limitations. So if I’m stuck on 21/32 for just one VLAN then there’s no hope of adding manual assignments for any of the other VLANs?

Too large in number I.e. too many assignments or too many characters for each entry e.g. if I used shorter assigned names (and maybe single digit or double digit addresses like 192.168.53.3 rather than 192.168.53.133) would that squeeze any more out of it?

[EDIT] It’s a shame that nvram runs out of room, I’m personally becoming more comfortable poking around inside folders and files and using amtm and adding etc on the router but I can imagine folks who just want to stick to the GUI and be able to add/delete/amend reservations there, as IoT device numbers expand, the ability to do so easily must have seemed within their grasp when they saw that menu option.

 

[dave14305]

/jffs/configs/dnsmasq-1.postconf

I assume there’s a typo somewhere here. Is this a postconf script or a config? Must be a conf because the postconf does not get numbered.

 

[jksmurf]

Have successfully created manual IP reservations for the two Guest Network Pro clients using /jffs/configs/dnsmasq-1.postconf (permissions 0644) and /jffs/configs/dnsmasq-2.postconf (permissions 0644) files. Correct names (from those postconf files) are correctly populated on the; Network Map, Client Status, Client List, Guest Network Pro client lists, and Wireless log sections. Examples for others (MAC address,IPAddress,ClientName):
/jffs/configs/dnsmasq-1.postconf

This is fantastic, thank you for taking the time to do that, with examples and appropriate file names, really appreciate it. Quick question, does it rely on YazFi or can I just upload the .postconf files?

 

[bennor]

This is fantastic, thank you for taking the time to do that, with examples and appropriate file names, really appreciate it. Quick question, does it rely on YazFi or can I just upload the .postconf files?

YazFi isn't coded for the 3006/Guest Network. So don't bother installing YazFi. Instead just use the /jffs/configs/dnsmasq-x.conf.add file for each of the Guest Network Pro (or Network) SDN's if doing manual IP reservations for each of the GNP SDN's.