ColinTaylor
Part of the Furniture
Thanks for the info @FernandoF. This build includes an updated version of
networkmap
for the RT-AC86U so perhaps that fixes something.networkmap
for the RT-AC86U so perhaps that fixes something.Thank you Colin, that sounds promising!Thanks for the info @FernandoF. This build includes an updated version ofnetworkmap
for the RT-AC86U so perhaps that fixes something.
I would like to start by saying a big thank you RMerlin for your work!
I've updated the firmware on an Asus RT-AC68U H/W ver. A1 router from 386.11_0 to 386.12_alpha1-g64a31d1c9e, keeping the settings.
I have a problem with ddns watchdog restarting the ddns update every 30 seconds, so after some troubleshooting, which got me nowhere, I've decided to do a hard reset, by holding wps button while powering on until power led starts blinking, to check if the issue is present after a minimal setup, after saving the config and jffs partition.
Thank you for trying to help. Yes, the gateway is from the client, also all other firmwares for my router have used 192.168.1.1 as the router lan ip, including but not limited to 386.11_0 and 3.0.0.4_386_51665, which both can be reset without issues. Icmp pings also confirm that the router is responding from this ip.Try 192.168.1.50 or 192.168.0.50
Edit: unless you are getting the gateway from your client, then never mind.
Thank you for your confirmation.I can confirm this issue on RT-AC68U
I have a single wan connection using pppoe, cg-nat ipv4, ipv6 enabled and ddns set to update ipv6, ddns service by noip.com and /jffs/configs/inadyn.conf.add file withOut of 6 routers I updated to 386.12 Alpha 1, 1x RT-AC88U did have DDNS restarting constantly but so far a reboot did fix it. I guess I'll check it again tomorrow
allow-ipv6 = true
and iface = ppp0
lines.http://192.168.1.1
or http://192.168.1.1:80
into the address bar of web browsers. Since this was not responding, firefox also tried https://192.168.1.1
.For the sake of troubleshooting (that is what alpha testing is for after all), did you save any logs (via ssh'ing into the router)? Without logs, there is not much the developer can do.Thank you for trying to help. Yes, the gateway is from the client, also all other firmwares for my router have used 192.168.1.1 as the router lan ip, including but not limited to 386.11_0 and 3.0.0.4_386_51665, which both can be reset without issues. Icmp pings also confirm that the router is responding from this ip.
Thank you for your confirmation.
I have a single wan connection using pppoe, cg-nat ipv4, ipv6 enabled and ddns set to update ipv6, ddns service by noip.com and /jffs/configs/inadyn.conf.add file withallow-ipv6 = true
andiface = ppp0
lines.
I've tried without the file, but inadyn will not update the the wan interface ipv6 address, instead it will update the real ipv4 address of the connection, so not the one assigned to the wan interface.
I would have tried a configuration from default settings, but that got me posting the original message.
Just to be clear, I've typedhttp://192.168.1.1
orhttp://192.168.1.1:80
into the address bar of web browsers. Since this was not responding, firefox also triedhttps://192.168.1.1
.
It was the first time in 9 years since I've had this router that I had to use the firmware restoration tool, but since this is an alpha version, it's kind of expected that not all things work properly. It was and still is a great buy.
As being able to reset the router by a non technically inclined person is important to me, for now I've returned the router to firmware 386.11_0 and restored the saved config file and jffs partition.
There is no way to access the logs via ssh after hard resetFor the sake of troubleshooting (that is what alpha testing is for after all), did you save any logs (via ssh'ing into the router)? Without logs, there is not much the developer can do.
I know, was just hoping you saved some before you hit the big red buttonThere is no way to access the logs via ssh after hard reset
If it doesn't, I see in the other thread that individuals took stab attempt at ChatGPT'ing a script to purge the Virtual Memory cache for networkmap, but @dave14305 pointed out their failures. Can you think up a script that could rectify this ordeal?Thanks for the info @FernandoF. This build includes an updated version ofnetworkmap
for the RT-AC86U so perhaps that fixes something.
I can't contribute to troubleshooting this or proposing a solution, but there's a newcomer to this place who seems interested in contributing:If it doesn't, I see in the other thread that individuals took stab attempt at ChatGPT'ing a script to purge the Virtual Memory cache for networkmap, but @dave14305 pointed out their failures. Can you think up a script that could rectify this ordeal?
I haven't been following this problem in detail as it's not something that effects me. If the memory usage is increasing fairly slowly I'd just create a cron job that killed that process in the middle of the night. The watchdog should restart it automatically and it's not like that process needs to always be running anyway.If it doesn't, I see in the other thread that individuals took stab attempt at ChatGPT'ing a script to purge the Virtual Memory cache for networkmap, but @dave14305 pointed out their failures. Can you think up a script that could rectify this ordeal?
There is no way to access the logs via ssh after hard reset
You can use the newer firmware to restore, you just need to use the the mini cfg server in recovery mode.Had to dig up a merlin 378 file to restore my ac68u, the 90+MB files whether official or merlin would fail.
You can use the newer firmware to restore, you just need to use the the mini cfg server in recovery mode.
Use a web browser and put in 192.168.1.1
Yes this one sucks big timeI wish i had seen your comment about the custom client icons before i went down the rabbit hole of trying to reset the JFS, it got me in this mess in the first place.
Yes this one sucks big time
updated my 2 rt-ac68u to this version both are working flawless.
Did any of you do a hard reset ?My RT-AC5300 is running perfectly on this alpha! No log weirdness or performance hitches noted...
Nope.Did any of you do a hard reset ?
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!