Hello...try running the beta script and see if this helps. You will need to enable dev mode and run an update of the script.if I want to view the status in realtime updates, do I open the monitor?
Hello...try running the beta script and see if this helps. You will need to enable dev mode and run an update of the script.if I want to view the status in realtime updates, do I open the monitor?
ok I guess I need to look for how to do this hahaHello...try running the beta script and see if this helps. You will need to enable dev mode and run an update of the script.
Access the Configuration Menu and Enable the following optionok I guess I need to look for how to do this haha
Configure Dev Mode
the cron job for failover is running now, is the beta very different than the current version I'm using? I'm just scared that it will not be stable when a failover should happenAccess the Configuration Menu and Enable the following option
Code:Configure Dev Mode
Once enabled check for updates and it should offer you to download the latest beta.
There are several enhancements and fixes in v2.0.1 for v2.0.0, it's not majorly different but you are likely to have better success on that build.the cron job for failover is running now, is the beta very different than the current version I'm using? I'm just scared that it will not be stable when a failover should happen
I've put wan failover on dev mode and updated, I got a message saying the update succeeded and on the menu it says version v2.0.1There are several enhancements and fixes in v2.0.1 for v2.0.0, it's not majorly different but you are likely to have better success on that build.
You Ctrl + C escaped the entire menu and restart over?I've put wan failover on dev mode and updated, I got a message saying the update succeeded and on the menu it says version v2.0.1
but on the status it still says I'm using 2.0.0 and out of date, also the status says wan failover is either not running or unresponsive, while I've tried killing the process several times through the menu and running it again
View attachment 48857
ahh why didn't I thought of that, silly meYou Ctrl + C escaped the entire menu and restart over?
If it sees one or both of the interfaces isn’t updating its ping / packet loss stats it will display that status.ahh why didn't I thought of that, silly me
Ok after killing all tasks and even now rebooting the router, it runs and shows the new version on the status
I am guessing it runs on startup since I when I check the status it seems to be running?
is unresponsive an expected value? I saw it as failover monitoring awhile ago but now it's back to unresponsive
View attachment 48866
Gotcha I will wait for a failover event to see if it's working as intended, thanks a lot for what you've builtIf it sees one or both of the interfaces isn’t updating its ping / packet loss stats it will display that status.
This is happening when you run install?Here are my current settings (LOAD BALANCE as I do not need failover):
View attachment 48889
And the problem is whenever I try and install the script on latest 388.2_beta1 on my GT-AX6000, all I am getting is this:
/jffs/scripts/wan-failover.sh: line 1: WANDOGTARGET: parameter not set
Tried several reboots and resets but always the same result. Anyone knows what I am doing wrong here? Thank you in advance for any help.
Many thanks indeed for the rapid fix. I have now installed as below:This is happening when you run install?
EDIT:
I released a minor patch (v2.0.2) to resolve your issue, no need for beta it is a minor fix and wasn't caught during beta cycle.
Yes the default settings should work and the failover monitoring has benefits in Load Balance Mode too. It will remove down WAN interfaces in Load Balance if they go down.Many thanks indeed for the rapid fix. I have now installed as below:
View attachment 48897
Is there anything else that I need to do or any other settings to change or is this all that is needed for the script (load balance function) to work? Many thanks again for your excellent work.
Superb. I am looking forward to trying it out as it looks really quite promising. Much appreciated.Yes the default settings should work and the failover monitoring has benefits in Load Balance Mode too. It will remove down WAN interfaces in Load Balance if they go down.
Let me know if you have any issues.Superb. I am looking forward to trying it out as it looks really quite promising. Much appreciated.
They are stored in the syslog but if you aren’t forwarding to a syslog server the router is only storing 1024 last logs and dumping the rest. Capture and monitor mode actively monitor the log and not historical logs.Hi, I just had a disconnection event happened today on my WAN0, but the wan failover didn't switch to the second connection, even after a few minutes, I ended up losing connection altogether while the WAN1 the second connection is still alive.
WAN0 Pings to 8.8.8.8 and I am also running the ping on a command window on my PC, the ping returns an RTO, however, wan failover didn't detect it or at least the status didn't change and no failover happened.
How do I view the logs to see what happened and to troubleshoot? I tried operations 11 to capture system log for failover events but that didn't return anything different to option 10.
Thanks in advance
I have a usb drive mounted on the router, is it possible to save the logs there?They are stored in the syslog but if you aren’t forwarding to a syslog server the router is only storing 1024 last logs and dumping the rest. Capture and monitor mode actively monitor the log and not historical logs.
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!