Ah yes, you're using an RT-AC86U as well....so describe the failure (Failover not happening, etc?) and the script is still running in the background, yes?And how to check that the script works and has not been unloaded from memory? I just had a failure on two routers, so both simply did nothing and I did not see any messages from the script in the logs.
I have ax88 and two ax86. It so happened that there was no Internet for an hour and 20 minutes, and so there were no messages from the script in the log. The routers worked without reboots for about a couple of days.Ah yes, you're using an RT-AC86U as well....so describe the failure (Failover not happening, etc?) and the script is still running in the background, yes?
This will tell you if the script is running:I have ax88 and two ax86. It so happened that there was no Internet for an hour and 20 minutes, and so there were no messages from the script in the log. The routers worked without reboots for about a couple of days.
I do not know how to check if the script is still running or has already hung, but there are no messages from it anymore.
ps | grep -v "grep" | grep -e "wan-failover.sh"
I have already restarted the routers. I will now watch.This will tell you if the script is running:
Code:ps | grep -v "grep" | grep -e "wan-failover.sh"
10-4, let me know how it goes.I have already restarted the routers. I will now watch.
Run the kill switch and let the cron job reload it.I am trying out the v1.4.7-beta version. We will see how well it works. Is there a way to restart the script? The reason I ask is I want to change some of the parameters that are manually set during the install, but I don’t want to go back through all those steps. If there is a way to just reload the script so it will pickup my changes made in the conf file that would be great.
Run the kill switch and let the cron job reload it.
Only 1 of the run or manual mode should be able to run, you probably will see 2-3PIDs thoughHow many instances of the script should be running?
Just keep in mind guys I don’t have this model to test with so I am doing incremental changes to see if they help overcome the issues with accessing NVRAM.I also just installed the beta. Now watching the syslog how long the script will be running.
I’ve only had 1 report of a person having issues with this model but I believe it was related to their ping target stopping ping responses or WAN0 dropping on them. It would work for hours and then all of sudden drop and switch to WAN1 because of 100% packet loss which just means the pings were failing. Other than that I’ve had no other complaints about the script using that model. Also keep in mind on boots WAN1 is going to come up Active first I believe because of the firmware (or atleast this is the observed behavior with some models including my own) and the script will switch it back to WAN0 once it starts up.Is the “normal” script working okay on the AX86U ?
I have a back up 100Mbps Cable service for $20/moWhat seems to be everyone's preferred, low-cost, emergency-only, fail-over option? Probably a good candidate for a poll question...
No ISP backup option. If internet is really needed, I can hot-spot to my phone (from any single client device I need to use).
If that isn't working either, nothing is that much of an emergency to need a monthly backup for.
And yes, I do live on the internet, for 'work' purposes.
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!