snapieee
Occasional Visitor
Can you access the router via ssh? If yes, try running the following to restart http service:This is what I did, and its still unusable. and its the same on multiple browsers.
Code:
service restart_httpd
Can you access the router via ssh? If yes, try running the following to restart http service:This is what I did, and its still unusable. and its the same on multiple browsers.
service restart_httpd
Did you end up doing this? How is this setup working for you with the Merlin firmware? I'm running almost the same setup GT-AXE16000 + (2) ET12 nodes (mixed backhaul - one node wired one 6Ghz) + another AXE-16000 as a node so that I have good coverage for my 6GHz devices...finally got the config right so now I'm getting ready to throw another wrench into the mix and move to the Merlin firmware. Never a dull moment.
The 1st thing to try in the Control Channel section is to uncheck the DFS box and set a fixed channel which I see it chose 36.These are my settings currently on 388.1 in the pictures below and these were the settings I tried on 388.2 - https://www.snbforums.com/threads/a...e-for-select-models.84524/page-14#post-836690
have to thank you could not take Asus AXE 100 interface now using Merlin again so much better 388.2 works wellYes, not all models are supported.
Download the firmwarefile you want to test at the nodes, log into the meshrouter and flash from:I don’t know how to roll back firmware on the nodes to test.
The 1st thing to try in the Control Channel section is to uncheck the DFS box and set a fixed channel which I see it chose 36.
Pinging 9.9.9.9 with 32 bytes of data:
Reply from 9.9.9.9: bytes=32 time=28ms TTL=60
Reply from 9.9.9.9: bytes=32 time=22ms TTL=60
Reply from 9.9.9.9: bytes=32 time=22ms TTL=60
Reply from 9.9.9.9: bytes=32 time=15ms TTL=60
Reply from 9.9.9.9: bytes=32 time=23ms TTL=60
Reply from 9.9.9.9: bytes=32 time=23ms TTL=60
Reply from 9.9.9.9: bytes=32 time=21ms TTL=60
Reply from 9.9.9.9: bytes=32 time=21ms TTL=60
Reply from 9.9.9.9: bytes=32 time=18ms TTL=60
Reply from 9.9.9.9: bytes=32 time=14ms TTL=60
Ping statistics for 9.9.9.9:
Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 28ms, Average = 20ms
Pinging 9.9.9.9 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 9.9.9.9:
Packets: Sent = 10, Received = 0, Lost = 10 (100% loss),
@Tech9 @Viktor Jaep - This facehugger of a problem just won't let me go
Even with no scripts and external logging, this happens (just trying to nail down frequency now), I may go and setup that scenario as again...Your monitoring obsession and excessive use of scripts is creating the issues. I look at your posts as regular spam in beta/release threads.
I created my SNB account just to be able to add my comment.I updated my RT-AX88U last week dirty from 388.1 and unlike all positive comments I had problems:
After a day or so we could not connect with one device, yet another device could (I recall only a guest on a guest nw configured with yazfi). Very often the device that couldn't connect had been sleeping or been switched off.
I think it's the time that the DHCP lease ran out: 86400.
Stopping wifi on for example my iPhone and/or switching from 5 to 2.4Ghz could trigger a disconnect.
First I thought it was only the wifi that had trouble but it turns out also the wired machines.
We were not able to get connected so the only solution was to reboot the router.
What's even more weird was that my MacBook and my iMac had netbiosd processes running berserk (after running Microsoft software), 140% and up -- only solution for this too was to reboot the mac.
I've tried:
- reflashing the same firmware
- reset to factory with the checkbox
- reset to factory with the back button
- again reflash 388.2
The problem remained, disconnects.
Last resort was to flash 388.1 back. I did a dirty flash of 388.1 and it has been running without a hitch!
Skynet, diversion, unbound everything works.
Not hindered by any knowledge what's going on under the hood, but there's something in 388.2 that's causing the not being able to reconnect and more (netbiosd).
Thanks for the reply.If you are having DHCP and DNS issues while running Diversion, then remove Diversion. If Diversion causes dnsmasq to crash, possibly because you are trying to use long lists on a low-powered CPU with limited RAM, then it will obviously also affect DHCP and DNS since both are also handled by dnsmasq.
I'm wondering too. I've been running the same setup for "ages" on my RT-AX88U and 388.1 was the most stable ever.Thanks for the reply.
I understand the recommandation but would like to know why it as working fine on 388.1 (and previous FW) and not on 388.2. Does the new version is so different than the previous one?
I thought that the Asus RT-AX86U was a good router and not a "low-powered CPU" (CPU : quad core @ 1.8 GHz, RAM : 1024, Flash : 256)
388.2 has a newer version of dnsmasq.Does the new version is so different than the previous one?
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!