@Dedel66 : The page you show works well for me as well. I meant: if you look at the scMerlin page (if you have installed), the Temperatures are blank. BTW, it was the same in v.386.8. So it is probablky a scMerlin issue.For me works perfect:
View attachment 46002
It was removed from the newer HND 5.04 devices. HND 5.02 devices like yours are fine.I just upgraded my GT-AX11000 and noticed that I still have an option for fullcone NAT. I thought this was removed?
Mine looked the same on Firefox and on Edge, too.Hello,
I have just upgraded to this version. The main page looks like this.
On Firefox:
View attachment 46006
On Edge browser:
View attachment 46007
Am I missing Firefox plugins...?
Many thanks for this new version and all your efforts in developing Merlin builds!
Thank you for the quick reply!MIne looked the same on Firefox and on Edge, too.
It is working properly after a couple of refreshing page commands on Firefox (Ctrl - F5).
lb._dns-sd._udp.6.0.0.192.in-addr.arpa
lb._dns-sd._udp.0.50.168.192.in-addr.arpa
lb._dns-sd._udp.107.244.1.10.in-addr.arpa
If you have the Channel bandwidth set at auto & you've enable 160MHhz...just a strange thing to report:
did a dirty upgrade from 386.7_2 to 388.1_0, did the manual reboot as suggested. Wifi 5ghz did not come online, 2,4 did.
After disable/save/re-enable/save 802.11ax / WiFi 6 mode wifi 5Ghz started working again
System info
- GT-AX6000
- now on 388.1_0 (the normal non ROG)
- different names for 2.4 and 5 Ghz
- internet by dutch ziggo with ipv6 enabled and working (saw a mention about ipv6 connectivity)
Hope this helps in any way. For me the issue is resolved but it might help development/others
Yes, as I got the info from another user, will fw it. As mentioned above, putting stock fw on mesh router fixes this ^Same problem here,
UI said the wired uplink not working,
but I think it is working alright.
View attachment 45997
First timer here.
I've always flashed my asus to merlin and want to do this for my ax82u. I have a ac86u in an AI mesh. Do both routers need to be on this firmware for the aimesh to work?
This is behavior by design.I just updated my AX86U router to 388.1. At the same time, I changed my second AX86U from an AP to a mesh node running stock Asus 388_21709. The two devices are connected via cable on the 2.5G ports. My question is about the guest networks. Guest network #1 has an option to use just the router or all mesh nodes. Guest network #2 doesn't have that option. And guest network #2 doesn't appear to broadcast on the mesh node. Is this the way it is supposed to work? If so, does anyone know why? I'm trying to use guest network #2 for IOT devices and some of them are much closer physically to the mnode and have trouble connecting to the router.
By the way, setting up the mesh node via cable was easy. The two devices are 3 floors away from each other, connected by about 60m of cable. The router found the mesh node without a problem.
/tmp/home/root# stubby -l
[00:09:38.538530] STUBBY: Read config from file /etc/stubby/stubby.yml
[00:09:38.539067] STUBBY: Stubby version: Stubby 0.4.2
[00:09:38.539345] STUBBY: DNSSEC Validation is OFF
[00:09:38.539499] STUBBY: Transport list is:
[00:09:38.539663] STUBBY: - TLS
[00:09:38.539820] STUBBY: Privacy Usage Profile is Strict (Authentication required)
[00:09:38.539978] STUBBY: (NOTE a Strict Profile only applies when TLS is the ONLY transport!!)
[00:09:38.540130] STUBBY: Starting DAEMON....
[00:09:41.161291] STUBBY: 1.1.1.1 : Conn opened: TLS - Strict Profile
[00:09:41.161775] STUBBY: 1.0.0.1 : Conn opened: TLS - Strict Profile
[00:09:41.217731] STUBBY: 1.1.1.1 : Verify passed : TLS
[00:09:41.238027] STUBBY: 1.0.0.1 : Verify passed : TLS
[00:09:50.305566] STUBBY: 1.1.1.1 : Conn closed: TLS - Resps= 2, Timeouts = 0, Curr_auth =Success, Keepalive(ms)= 9000
[00:09:50.305627] STUBBY: 1.1.1.1 : Upstream : TLS - Resps= 2, Timeouts = 0, Best_auth =Success
[00:09:50.305653] STUBBY: 1.1.1.1 : Upstream : TLS - Conns= 1, Conn_fails= 0, Conn_shuts= 0, Backoffs = 0
[00:09:50.398773] STUBBY: 1.0.0.1 : Conn closed: TLS - Resps= 2, Timeouts = 0, Curr_auth =Success, Keepalive(ms)= 9000
[00:09:50.398831] STUBBY: 1.0.0.1 : Upstream : TLS - Resps= 2, Timeouts = 0, Best_auth =Success
[00:09:50.398859] STUBBY: 1.0.0.1 : Upstream : TLS - Conns= 1, Conn_fails= 0, Conn_shuts= 0, Backoffs = 0
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!