Release Asuswrt-Merlin 3006.102.4 is now available

[bennor]

@ElmerFudd, YazFi does not work, and is not supported, on the Asus-Merlin 3006.102.x firmware. If you had YazFi installed prior to installing 3006 firmware and you did not either install it, or do a reset/hard factory reset after flashing to 3006, you may have portions of YazFi left over on your system which may possibly be causing issues. There are a number of past posts and discussions that can be found using the forum search feature that talk about how to replicate, some with mixed results, certain YazFi features, including manual IP address reservations for Guest Network Pro clients, on the 3006 firmware.

For assigning manual IP reservations to Guest Network Pro Profile clients, when one configures the Use same subnet as main network option to disabled, one has several options. First is to use the new option under the Guest Network Pro Profile called Manually Assign IP around DHCP list. It will let one assign manual IP addresses, DNS address, and Host Name for the client.

The other option, discussed both earlier in this release discussion and in other past discussions is to use either a dnsmasq-snd.conf.add or dnsmasq-sdn.postconf file that are mentioned in the Asus-Merlin 3006 change log.

- NEW: Added dnsmasq-INDEX.conf.add and stubby-INDEX.yml.add,
which are appended to SDN config files (INDEX = SDN
index number)
- NEW: Added dnsmasq-sdn.postconf and stubby-sdn.postconf.
They take two arguments:
- path to the config file for that SDN's instance
- the SDN index number (1 for the first SDN instance)

Personally on a RT-AX86U Pro running Asus-Merlin 3006.102.4 I use a dnsmasq-1.conf.add (br52) and dnsmasq-2.conf.add (br53) file in the router's /jiffs/configs directory to assign client IP addresses to my two Guest Network Pro (IoT) Profiles. Works well and they are also reflected properly in my Pi-Hole logs after correctly configuring DNS Director to include my Pi-Hole device(s). Example dnsmasq-1.conf.add:

dhcp-host=AC:4F:22:99:AA:BB,set:AC:4F:22:99:AA:BB,SmartPlug1,192.168.52.21
dhcp-host=CF:4F:33:88:CC:DD,set:CF:4F:33:88:CC:DD,SmartPlug2,192.168.52.22
dhcp-host=GC:F4:32:11:EE:FF,set:GC:F4:32:11:EE:FF,SmartPlug3,192.168.52.23
dhcp-host=SC:F4:32:33:GG:HH,set:SC:F4:32:33:GG:HH,SmartPlug4,192.168.52.24

Adjust the code including file name as needed for one's use case, client MAC address, client hostname, and client Guest Network Pro IP address.

 

[Seth Harman]

So I upgraded and the guest network pro does not seem to be working correctly. If I configure Guest network pro to use different subnet, DHCP does not work even when configured under guest network pro for that subnet.... devices do not get an IP. I can manually assign the correct IP and the new guest network pro works so I confirmed it is DHCP. The only way to get my IOT to work without YAZFI now is to have them on all the same subnet which defeats the purpose.

Has anyone figured out how to get DHCP to work for a guest network Pro VLAN? I am using a AX88U pro.

Are you using AiMesh and, if so, are your nodes all on the 3006-revision firmware? We were just discussing this in another thread; if your AiMesh nodes are not on 3006 your wireless clients connecting to a node are not going to get tagged with the correct ID for any GNP instance you've created and set to have a different subnet from the main network. If you aren't using AiMesh and you just have the AX88U Pro something is probably configured wrong on your end as I also have an AX88U Pro and wireless GNP clients are working perfectly (including when connecting to one of my two AiMesh nodes running 3006).

 

[ElmerFudd]

@ElmerFudd, YazFi does not work, and is not supported, on the Asus-Merlin 3006.102.x firmware. If you had YazFi installed prior to installing 3006 firmware and you did not either install it, or do a reset/hard factory reset after flashing to 3006, you may have portions of YazFi left over on your system which may possibly be causing issues. There are a number of past posts and discussions that can be found using the forum search feature that talk about how to replicate, some with mixed results, certain YazFi features, including manual IP address reservations for Guest Network Pro clients, on the 3006 firmware.

For assigning manual IP reservations to Guest Network Pro Profile clients, when one configures the Use same subnet as main network option to disabled, one has several options. First is to use the new option under the Guest Network Pro Profile called Manually Assign IP around DHCP list. It will let one assign manual IP addresses, DNS address, and Host Name for the client.

The other option, discussed both earlier in this release discussion and in other past discussions is to use either a dnsmasq-snd.conf.add or dnsmasq-sdn.postconf file that are mentioned in the Asus-Merlin 3006 change log.

Personally on a RT-AX86U Pro running Asus-Merlin 3006.102.4 I use a dnsmasq-1.conf.add (br52) and dnsmasq-2.conf.add (br53) file in the router's /jiffs/configs directory to assign client IP addresses to my two Guest Network Pro (IoT) Profiles. Works well and they are also reflected properly in my Pi-Hole logs after correctly configuring DNS Director to include my Pi-Hole device(s). Example dnsmasq-1.conf.add:

dhcp-host=AC:4F:22:99:AA:BB,set:AC:4F:22:99:AA:BB,SmartPlug1,192.168.52.21
dhcp-host=CF:4F:33:88:CC:DD,set:CF:4F:33:88:CC:DD,SmartPlug2,192.168.52.22
dhcp-host=GC:F4:32:11:EE:FF,set:GC:F4:32:11:EE:FF,SmartPlug3,192.168.52.23
dhcp-host=SC:F4:32:33:GG:HH,set:SC:F4:32:33:GG:HH,SmartPlug4,192.168.52.24

Adjust the code including file name as needed for one's use case, client MAC address, client hostname, and client Guest Network Pro IP address.

@bennor I did a hard reset before installing latest firmware and reformatted USB stick with new scripts / swap. So it does not appear to be a conflict with YAZFI…. I did read it would not work prior and was hopeful I could get same subnet capability with a from sratch install and Guest network pro vlans.

Will the DNS masq files allow me to use differnt subnets on guest networks? I really do not want my IOT on same subnet as core network. IMHO, it’s best to keep those potentially tainted devices in their own jail isolated from rest of devices. Wish VLANs worked with different subnets as that would be ideal.

 

[ElmerFudd]

Are you using AiMesh and, if so, are your nodes all on the 3006-revision firmware? We were just discussing this in another thread; if your AiMesh nodes are not on 3006 your wireless clients connecting to a node are not going to get tagged with the correct ID for any GNP instance you've created and set to have a different subnet from the main network. If you aren't using AiMesh and you just have the AX88U Pro something is probably configured wrong on your end as I also have an AX88U Pro and wireless GNP clients are working perfectly (including when connecting to one of my two AiMesh nodes running 3006).

Not using AImesh. Did a hard reset on AX88U pro before reconfiguring and repartitioning and formatting USB stick with fresh scripts and swap.

Does a hard reset clear JFFS or did I need to do that manually? That’s only thing I can think of.

 

[MDM]

Not using AImesh. Did a hard reset on AX88U pro before reconfiguring and repartitioning and formatting USB stick with fresh scripts and swap.

Does a hard reset clear JFFS or did I need to do that manually? That’s only thing I can think of.

But did you try without the scripts? That is the point...

 

[ElmerFudd]

But did you try without the scripts? That is the point...

I can try a night this week and report back. Only scripts I’m running is Skylnet and AddGuard Home. Already tried disabling skynet but did not uninstall.

 

[dave14305]

I can try a night this week and report back. Only scripts I’m running is Skylnet and AddGuard Home. Already tried disabling skynet but did not uninstall.

Adguard home installer has a few conflicts with the new firmware and hasn’t been updated yet.

 

[bennor]

Will the DNS masq files allow me to use differnt subnets on guest networks?

Yes. When you set Use same subnet as main network to disable the Guest Network Pro Profile will configure a separate IP subnet, it generally defaults to 192.168.52.x for the first GNP, then 192.268.53.x for the second and so on. There is an option in Guest Network Pro to change the IP subnet range to something else.

Gest Network Pro VLAN's, once created, can have their own subnets provided one disables Use same subet as main network.

Seriously, just try it out. That is how some of us figured all this stuff out, through trial and error, for our use case since there isn't much documentation from Asus on the specifics of the Guest Network Pro feature.

Edit to add: Example GNP IoT profile's advanced settings attached showing the profile's LAN IP option and enable DHCP server option.

 

[bennor]

Not using AImesh. Did a hard reset on AX88U pro before reconfiguring and repartitioning and formatting USB stick with fresh scripts and swap.

A number of addon scripts do not work or need to be updated to work with the Asus-Merlin 3006 firmware. See the following if you haven't done so already...
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006

amtm - Announcing AMTM-OSR, AMTM Orphaned Script Revival repository

Life just happens - to all of us. Interests and priorities change and we get older everyday. Some are no longer with us, others have moved on to other pastures. We're all glad you were part of this amazing community. So, thank you to all of you for what you contributed script wise. You know who...

www.snbforums.com

 

[Paliv]

Thanks @bennor and @MDM for your suggestions. I ended up blocking 8888 and 8844 in Network Services Filter for each device, and that worked.

 

[ElmerFudd]

Yes. When you set Use same subnet as main network to disable the Guest Network Pro Profile will configure a separate IP subnet, it generally defaults to 192.168.52.x for the first GNP, then 192.268.53.x for the second and so on. There is an option in Guest Network Pro to change the IP subnet range to something else.

Gest Network Pro VLAN's, once created, can have their own subnets provided one disables Use same subet as main network.

Seriously, just try it out. That is how some of us figured all this stuff out, through trial and error, for our use case since there isn't much documentation from Asus on the specifics of the Guest Network Pro feature.

Edit to add: Example GNP IoT profile's advanced settings attached showing the profile's LAN IP option and enable DHCP server option.

Thank you. will try it out.

 

[ElmerFudd]

Adguard home installer has a few conflicts with the new firmware and hasn’t been updated yet.

@dave14305 & @bennor Thank you. Will try without any scripts.

 

[Seth Harman]

Not using AImesh. Did a hard reset on AX88U pro before reconfiguring and repartitioning and formatting USB stick with fresh scripts and swap.

Does a hard reset clear JFFS or did I need to do that manually? That’s only thing I can think of.

If you just have the RT-AX88U and no other hardware in the mix (no AiMesh nodes, no APs connected to the network, etc...) then this is what you should be seeing: if you create an instance in Guest Network Pro, name it IOT, configure it to not use the same subnet as the main network, and it's showing you a VLAN ID of 52, then any wireless client connecting to the "IOT" wireless network that is not configured in some way to receive a fixed IP address will get a DHCP address from the 192.168.52.x IP block. Turn off all scripts and see if that's the behavior you're experiencing, if it isn't I'd recommend you nuke everything, reinstall the firmware, test it and, if it's now working, start adding scripts back in one at a time to see what breaks it.