What's new
  • 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.102_4 alpha Build(s) ] available build(s)

Have loaded new alpha2 and most seems fine.....
Software not load first time, have to turned off DNS over TLS, Unmounted USB and turned off all killswitch.

Have to create new guestnetwork on 5GHz, but that according to changelog.





Thanks for the new software
 
Last edited:

I don't see the Aura RGB-light mentioned but it sure has a connection. No biggie but it was nice to boot with leds on, aura off.
 
I don't see the Aura RGB-light mentioned but it sure has a connection. No biggie but it was nice to boot with leds on, aura off.
As those links indicated he changed the way the Asus-Merlin firmware handles LED's. If you look at the code changes at the following link you'll see he removed the Asus-Merlin firmware code that controlled the LED's turning on based on router model. For example the GTAX11000_PRO.
It is possible by reverting back to letting the Asus closed source code handle the LED's, that closed source code may be the issue, or how it's called may be the issue, with your specific router.
 
Last edited:
I think I found what's causing my dcd errors. I had Guest Network 2.5 and 5 setup manually for some WPA2 hardware same as the previous stable firmware but these GN's is causing to dcd errors with this Alpha. When I turned them(GN) off the dcd stopped.

@RMerlin
Update: Tried to enable GN2.4 and left GN5.0 disabled, no dcd errors. Once both were on, dcd errors shows its ugly head again. :)
 
Upgraded first alpha 2 to second alpha 2 this evening on my GT-AX6000.

Router now keeps losing the connection my IoT devices on the IoT (Guest Pro) network 😢

(a few seconds after every reboot)
 
First downgraded to the first 3006 alpha 2. Connections seemed a bit more stable, but ping to devices in the same room as the router had a "time" of more than 2000 ms.

Next downgraded to 3004 and restored the 3004 settings. Initially had connectivity issues as well, but they seem stable now and ping to those devices is less than 20 ms.
 
Filthy upgrade from old Alpha 2. No issues so far - will report back if anything jumps out.
 
Upgraded from alpha 1 to alpha 2, I had to reinstall unbound GUI add-on to be able to access the tabs for the add-ons I have installed - scmerlin, ntpmerlin, spdmerlin & unbound.
 
@dave14305 Dave, I believe you were wondering about FlexQoS on this code level? All the GUI seems correct (was an error on earlier 3006.102.3 level), Note, no Rate Date though. All seems ok on this Alpha1 level.

1742947026788.png

1742947145131.png
 
AP mode works like that. Mine is the same as yours.
An AP is just a bridge. The AP has no idea what the client's IP address or hostnames are, unless some of that info shows up in the AP's ARP cache.
 
First downgraded to the first 3006 alpha 2. Connections seemed a bit more stable,
That alone tells me your problem is not the firmware. There was zero changes to the wifi code between alpha builds, so any difference in performance means the issue is your configuration or your environment. Most common cause is people having the channel set to Auto, and ending up on different channels between firmware changes.

Initially had connectivity issues as well,
And this as well.
 
Hmmm, nice to learn something new, thought that DNS was separate from the subnet IP question; simply did not think about how it was routed trough it.
I've now changed the DNSDirector code so when a GN has DNSDirector set to "Router" and is on its own separate VLAN/subnet, it will now properly use that subnet's IP instead of the primary LAN IP.
 
That alone tells me your problem is not the firmware. There was zero changes to the wifi code between alpha builds, so any difference in performance means the issue is your configuration or your environment. Most common cause is people having the channel set to Auto, and ending up on different channels between firmware changes.


And this as well.
My channel is fixed, set to the least crowded channel (checked yesterday that it’s still the least crowded).

PS: I’m not blaming the firmware (I have seen the “zero changes” response many times before); merely stating what I did and what I observed. I hope to experiment with this or a future build again (or booting 3004 a couple of times), when I have some more time, to try to understand what’s going on.
 
It's not, see previous posts on this topic.
Thanks, now I made further tests and discovered the culprit was ControlD daemon (as I have DNS director off). I'll report to them.

And regarding GN scheduling? I scheduled to turn on on the weekend, but on week days some bands still keep on and usable.
 
If I leave DNS set to "Default" in the advanced setting of a 3006 Guest Network, what does "Default" refer to?

The DNS severs from my ISP? Or the DNS servers I set up for the router? Or the DNS server I set up for the regular/main network?
 
I've now changed the DNSDirector code so when a GN has DNSDirector set to "Router" and is on its own separate VLAN/subnet, it will now properly use that subnet's IP instead of the primary LAN IP.
Great news, so now even the GN can benefit of DNSSEC and DoH!
Thank you for you efforts as always.

I am also curious about XIII question about the meaning of "Default" for GN DNS...
 

Similar threads

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!
Back
Top