Release Asuswrt-Merlin 3006.102.4 is now available

[cc666]

Technically yes it is a bug. One that has been there for a while with the Network Map. The Network Map just gets wonky from time to time. As others already indicated, the Network Map may fix itself after a period of time or if you kill and restart the Network Map process. I've found that when making a change to a Guest Network Pro profile, sometimes the profile number of client indicator (indicated by the yellow highlight box in the image below) doesn't refresh properly for a period of time. Likely gets refreshed when the Guest Network Pro profile's client lease time is renewed.
View attachment 65889

This does not happen on the latest stock firmware.

Also another dilema, i decided to reset and input all my settings manually. For some reason the router would not connect to the internet after the reset, saying DHCP server error. I tried everthing and nothing fixed the problem. I then reflashed the stock firmware, uoloaded a config file and everthing was back to normal. Why did that happen? any idea

CC

 

[bennor]

This does not happen on the latest stock firmware.

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro. I normally just ignore it when it happens as it usually corrects itself (in both locations) after a short period of time. YMMV and all that.

 

[CaptainSTX]

I was using only AES. Besides i think it would not connect in that case completely.

One way to test is setup a guest network that is open with no encryption and see if the problematic clients will connect. If they will then the problem is probably the encryption. Not recommending you run long term with no encryption and what I did was install an old travel router as an AP just for this device with AES-TKIP encryption.

 

[cc666]

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro. I normally just ignore it when it happens as it usually corrects itself (in both locations) after a short period of time. YMMV and all that.

OK, any ideas on not connecting to internet? I had to go back to stock. I tried everything.

CC

 

[bennor]

OK, any ideas on not connecting to internet? I had to go back to stock. I tried everything.

No idea without more information. Where were you seeing the "DHCP server error"? Did you check the router log to see what it indicated for the internet loss?

 

[128bit]

May not have happened for you, but I've experienced the Network Map not properly updating and the Guest Network Pro profile client list and client tab not updating correctly on pretty much all the iterations of the stock Asus 3006.102.x firmware for the RT-AX86U Pro.

. . . which segues nicely to this question: what's the latest guidance on having the mesh node on merlinware as opposed to stockware?

 

[bbunge]

I "tested" 3006.102.4 on my AX86U Pro again yesterday. Enabled DoT, DNS Director (Router) and installed AMTM, Entware and Diversion. Everything seemed to be working but out of curiosity I opened a terminal and ran "stubby -l" to check the DoT operation. Normally I should see the connections going to the upstream resolvers. But, there was no results shown. I removed Diversion and turned off DNS Director and tried "stubby -l" again. Nothing. Sorry but I did not check the router log before I went back to Asus firmware. Am reporting this as a possible issue.

Update: Back to 3006.102.4. Set up the AX86U Pro with pretty basic settings. To test DoT I set up Cloudflare (1.1.1.1, 1.0.0.1) in the DoT area. I then went to "https://one.one.one.one/help/" to check if the router was connected to Cloudflare and if it was using DoT. It was. Back to the command prompt where "stubby -l" just showed that Stubby had started. Web research showed that "stubby -v 7" should show the connections. It didn't but as I felt convinced that the DoT was working I moved on to finish configuring the router.