Beta Asuswrt-Merlin 3006.102.4 Beta is now available

[jksmurf]

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

Thank you, by one of the scripts you mean I can either install YazDHCP or as you described here I can either

add static DHCP entries using either the /jffs/configs/dnsmasq.conf.add config file or the /jffs/scripts/dnsmasq.postconf script.

For the simple approach, without scripts I can presumably just add (x=index) numbered dnsmasq-x.conf.add config files populated with the details shown in @bennor example above for VLANs?

[EDIT] Seems to have been confirmed by @bennor below.

 

[bennor]

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.

No not a typo. The /jffs/configs/dnsmasq-1.postconf file is a "config" file, not a "script" file. Edit to add: Sorry for the confusion, in a hurry and made a typo. The correct file is dnsmasq-1.conf.add and dnsmasq-2.conf.add in the /jffs/configs/ directory.

You use the SDN index number in the file name. Note what RMerlin indicated and explained in the 3006.201.1 change log:

3006.102.1 (28-Jun-2024)
- 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)

 

[jksmurf]

YazFi isn't coded for the 3006/Guest Network. So don't bother installing YazFi. Instead just use the /jffs/configs/dnsmasq-#.postconf file for each of the Guest Network Pro (or Network) SDN's.

Thank you. The # numbering is the chronological order of creation of the VLANs e.g if I created 53 first then 52 later, 52, 53= 2,1 or the numbering order if the VLANs I.e. 52, 53 = 1, 2 etc?

 

[bennor]

Thank you. The # numbering is the chronological order of creation of the VLANs e.g if I created 53 first then 52 later, 52, 53= 2,1 or the numbering order if the VLANs I.e. 52, 53 = 1, 2 etc?

See post above yours, as indicated in the change log; "the SDN index number (1 for the first SDN instance)".

 

[dave14305]

No not a typo. The /jffs/configs/dnsmasq-1.postconf file is a "config" file, not a "script" file

Then please correct your posts with the correct file extension (.conf.add).

 

[ColinTaylor]

No not a typo. The /jffs/configs/dnsmasq-1.postconf file is a "config" file, not a "script" file. You use the SDN index number in the file name. Note what RMerlin indicated and explained in the 3006.201.1 change log:

3006.102.1 (28-Jun-2024)
- 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)

This seems to contradict what you're saying.

I would expect dnsmasq-INDEX.conf.add to be a config file (in /jffs/configs/) and dnsmasq-sdn.postconf to be a script ( /jffs/scripts/).

 

[jksmurf]

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

Sorry I meant YazDHCP, not YazFi. But presumably I don’t absolutely need it, I would only use it for import / export. i.e. the conf files are fine.

See post above yours, as indicated in the change log; "the SDN index number (1 for the first SDN instance)".

Just saw your post on that, so that suggests order of SDN creation. Out of curiosity, if you were hunting for it later, is there a file which relates instance to VLAN ID?

 

[bennor]

@dave14305 and @ColinTaylor, you guys were correct. Sorry for the confusion. Realized after the fact I grabbed the wrong file name from my notes as I was experimenting with both the /jffs/configs/dnsmasq-1.postconf and dnsmasq-1.conf.add files in an effort to experiment and was in a hurry to make the post here before moving on to other things.. Went and looked back at the router and it is the dnsmasq-x.conf.add file. Prior post has been updated to reflect the correction.

 

[jksmurf]

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.

I recorded a few inconsistencies in the Network Map at the alpha stage but unfortunately the Network Map at least (Wireless log is fine) is one of those animals that RMerlin has no control over.

 

[Jeffrey Young]

Thank you, by one of the scripts you mean I can either install YazDHCP or as you described here I can either



For the simple approach, without scripts I can presumably just add (x=index) numbered dnsmasq-x.conf.add config files populated with the details shown in @bennor example above for VLANs?

[EDIT] Seems to have been confirmed by @bennor below.

I would be careful with YazDHCP with 3006 until the developer or someone else can confirm YazDHCP will work. I don't use it, so I can't say.

You are correct though about the dnsmasq scripts and config files.

 

[David Williams]

Updated main router and two mesh nodes:
Main Router - RT-BE96U
Mesh Notes - RT-AX86U Pro's

All upgrades worked without issue.

Thanks!!!

 

[bennor]

I would be careful with YazDHCP with 3006 until the developer or someone else can confirm YazDHCP will work. I don't use it, so I can't say.

There is more discussion about YazDHCP (and other add-ons) and the 3006 firmware at the following link. General consensus appears to be the YazDHCP develop version (1.0.7), that user Martinski has been updating from time to time to fix issues, works with 3006.
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006

The original developer (Jack Yaz) is no longer apparently actively developing his scripts.

 

[Jeffrey Young]

There is more discussion about YazDHCP (and other add-ons) and the 3006 firmware at the following link. General consensus appears to be the YazDHCP develop version (1.0.7), that user Martinski has been updating from time to time to fix issues, works with 3006.
https://www.snbforums.com/threads/c...ons-with-gt-be98-pro.90657/page-7#post-947006

The original developer (Jack Yaz) is no longer apparently actively developing his scripts.

Perfect, I had not been keeping up. Glad to see that someone has been modifying the script to work with the new sdns

 

[outlaw78]

Asuswrt-Merlin 3006.102.4 Beta is now available. There are a number of significant things to note with this release:

- NOTE: As a reminder, the ROG variant of the webui is not
supported in the 3006 firmware series, as maintaining
two separate interfaces is too much extra work.

Ah, this is unfortunate. I've found that using the non-rog version of Merlin is "buggy". I've been waiting for an update with the ROG version since 8_2. I migrated to 8_4 but went back to 8_2 since it had the ROG gui.

Is it not supported by stock Asus firmware or just Asus-Merlin?

 

[RMerlin]

Is it not supported by stock Asus firmware or just Asus-Merlin?

By me. Asus is the opposite - they only support the ROG GUI on these devices.

 

[outlaw78]

By me. Asus is the opposite - they only support the ROG GUI on these devices.

Well I hope you change your mind at some point in the future. Twice the ROG Gui was missed (that I am aware of) in the firmware updates, and both times I used the normal Gui, my AXE-16000 would do wierd things that constantly required a reboot when so I just ended up downgrading to the previous version of firmware that had it. Is there any coding changes between the two or is simply a graphical interface? I did notice some of the features were missing in the non-rog gui?

 

[Howard_inGA]

Well I hope you change your mind at some point in the future. Twice the ROG Gui was missed (that I am aware of) in the firmware updates, and both times I used the normal Gui, my AXE-16000 would do wierd things that constantly required a reboot when I just ended up downgrading. Is there any coding changes between the two or is simply a graphical interface? I did notice some of the features were missing in the non-rog gui?

Same gear here, and no major glitch with Merlin's latest Beta...

 

[outlaw78]

Same gear here, and no major glitch with Merlin's latest Beta...

That's awesome! I still prefer the ROG Gui. In addition to the weird issues I had, I also missed the extra information the ROG Gui gives on home screen pertaining to the game side of things. I'll give a try when it comes out of beta, but I really disapointed to find that the ROG Gui is going to be by-passed. Other than that, Merlin firmware is the best for the fact he keeps things like oVPN updated and such.

 

[GaselK]

I recorded a few inconsistencies in the Network Map at the alpha stage but unfortunately the Network Map at least (Wireless log is fine) is one of those animals that RMerlin has no control over.

The most annoying bug is that despite IoT (SDN) network is disabled by schedule, IoT devices keep connecting to it.

 

[Ripshod]

Is anyone actually having issues with YazDHCP? Because I'm not seeing any problems in my setup.