Beta Asuswrt-Merlin 3006.102.6 Beta is now available

[dwadj]

I got a AiMesh setup with guest network pro setup for the IOT devices.
Main router GT-AX11000 pro is running 3006.102.6_beta2 as well as the Aimesh node GT-AX11000 pro.

The Reolink is connected on a AiMesh node (GT6) with the IOT network.
However it is not shown as IOT device in guest network pro.

All other IOT devices are in the guest network pro.
Is this an issue with the GT6 nodes since they only have stock firmware 388_24675?

Second issue.
I disabled the Aura light on all.
However on reboot the 2 GT6 nodes have the aura light again enabled.
I always need to disable it through the app.

 

[Jom76]

Updates my AXE16000 to Merlin 3006.102.6_beta2 from 3006.102.4...

Sonos speakers are throwing continuously the following message:

Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:53 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:55 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:53:59 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:03 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:05 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.162 48:a6:b8:5a:2f:42
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPDISCOVER(br52) 192.168.52.154 48:a6:b8:5a:31:b2
Nov 21 10:55:09 dnsmasq-dhcp[5978]: DHCPOFFER(br52) 192.168.52.154 48:a6:b8:5a:31:b2

Not sure why they won't connect anymore.
Any suggestions?

I have the same issues with sonos with RT-BE86U. I'm running Merlin firmware 3006.102.5, not the beta.
Look at my post in another thread for possible workaround https://www.snbforums.com/threads/issues-with-sonos-since-the-latest-update.95555/page-2#post-968977
Not the best workaround but it works. Hopefully the sonos issue will be solved in a future release of either sonos firmware or asus firmware. If you dont have this problem with firmware 3006.102.4 perhaps the issue was introduced in 3006.102.5? I might try downgrading if it's possible to do that?

 

[Dedel66]

Adding custom icons to a DHCP reservation doesn't work as usual. ***.png files cannot be used. Only the built-in default icons work. Existing custom icons are displayed correctly, but new saved icons are not.

 

[Ripshod]

Adding custom icons to a DHCP reservation doesn't work as usual. ***.png files cannot be used. Only the built-in default icons work. Existing custom icons are displayed correctly, but new saved icons are not.

Working fine with YazDHCP though.

 

[Dedel66]

Working fine with YazDHCP though.

Yes, that´s correct. Restoring icons with YAZDHCP works perfectly, but uploading a new image in ***.png format does not (as before).
Unfortunately, overwriting with a new icon no longer works either.

 

[Ripshod]

Yes, that´s correct. Restoring icons with YAZDHCP works perfectly, but uploading a new image in ***.png format does not (as before).
Unfortunately, overwriting with a new icon no longer works either.

I did have a problem adding a new custom icon, but rebooting the router and ssh'ing into YazDHCP and using option 1 to refresh the client list fixed it. Custom icon (png) accepted.
I think it's possibly a YazDHCP thing - in fact I'm sure it is.

 

[ComputerSteve]

I got a AiMesh setup with guest network pro setup for the IOT devices.
Main router GT-AX11000 pro is running 3006.102.6_beta2 as well as the Aimesh node GT-AX11000 pro.
View attachment 69153
The Reolink is connected on a AiMesh node (GT6) with the IOT network.
However it is not shown as IOT device in guest network pro.
View attachment 69154
All other IOT devices are in the guest network pro.
Is this an issue with the GT6 nodes since they only have stock firmware 388_24675?

Second issue.
I disabled the Aura light on all.
However on reboot the 2 GT6 nodes have the aura light again enabled.
I always need to disable it through the app.

GuestNetwork Pro doesn't work correctly with mixed firmwares - At least that seems to be the consensus

 

[Dedel66]

I did have a problem adding a new custom icon, but rebooting the router and ssh'ing into YazDHCP and using option 1 to refresh the client list fixed it. Custom icon (png) accepted.
I think it's possibly a YazDHCP thing - in fact I'm sure it is.

Thanks for your tips, unfortunately nothing worked:
I rebooted the router, updated YAZDHCP to 1.24, rebooted again, then selected 1 in YAZDHCP per SSH.

Unfortunately, no luck. The ***.png files, which always worked before, no longer do.

 

[maxbraketorque]

No operational issues with beta2 on my GT-AX6000 main/AP combo. Site-to-site VPN to two remote locations, a bunch of manual DHCP entries, Guest Network Pro on default bridge, a few firewall-start scripts, DoT enabled. As usual, the Client List isn't 100% accurate, but it seems to be a little better than perhaps 102.4 which is the last time I paid attention to it.

I did notice a cosmetic issue in the "Client Status" list as shown in the attached. The arrow is pointing to an unneeded curly quote. Its not present after any of the other IP addresses in my list, including one that ends in .254. Maybe an issue with 3-digit ending in zero?

Also, should "status" be capitalized? Title case seems to be in-use for most other items.

 

[David Cavalli]

Unfortunately, no luck. The ***.png files, which always worked before, no longer do.

Custom icon files are ultimately working fine. (For me at least.) I'm assuming you're historically using your icon.png files with YazDHCP and it does some conversion. However, if you're just interested in getting it to work, you can convert the .png files to the internal .log file, name it as the MAC-ID.log, and copy it to the /jffs/usericon directory.

Details here: How to install custom icons

Hope that helps!

 

[John Adler]

How to correct this notifications?
Thks for your comments

 

[Dedel66]

Custom icon files are ultimately working fine. (For me at least.) I'm assuming you're historically using your icon.png files with YazDHCP and it does some conversion. However, if you're just interested in getting it to work, you can convert the .png files to the internal .log file, name it as the MAC-ID.log, and copy it to the /jffs/usericon directory.

Details here: How to install custom icons

Hope that helps!

Thank you so much for your help and for pointing me to your instructions. It's too much work for me just to add a few nice icons.

I'm wondering, though, what exactly was changed and when? Is the conversion missing in YAZDHCP?

 

[RMerlin]

3006.102.6 final is now available. Thanks to everyone who participated in this beta cycle.