Confirmed via correct interface.
Doing now using 14b and restarting. Update: Didn't help, still think WAN1 is down.
Syntax error:
Code:
syntax error: unexpected "("WANFailover Dual WAN Failover Script
- Thread starter Ranger802004
- Start date
Doing now using 14b and restarting. Update: Didn't help, still think WAN1 is down.
Syntax error:
Ranger802004
Very Senior Member
Do you have NAT enabled for your secondary WAN?
NAT enabled - Symmetric on both Primary and Secondary.
Ranger802004
Very Senior Member
I forgot the $ in front of each (, sorry I’m on my phone typing. I edited original post
Last edited:
Bam we have success
Code:
Aug 14 17:51:07 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 17:51:07 router wan-failover.sh: Debug - Setting WAN0 Status for Check IP Rules
Aug 14 17:51:07 router wan-failover.sh: Debug - wan0 NAT Enabled: 1
Aug 14 17:51:07 router wan-failover.sh: Debug - Setting WAN0 Status for Check IP Rules
Aug 14 17:51:07 router wan-failover.sh: Debug - wan1 NAT Enabled: 1
Aug 14 17:51:07 router wan-failover.sh: Debug - WAN0STATUS: CONNECTED
Aug 14 17:51:07 router wan-failover.sh: Debug - WAN1STATUS: CONNECTED
Aug 14 17:51:07 router wan-failover.sh: Debug - WAN1 is Connected
Aug 14 17:51:07 router wan-failover.sh: Debug - Function: wan0failovermonitor
Aug 14 17:51:07 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 17:51:07 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 17:51:07 router wan-failover.sh: WAN0 Failover Monitor - Monitoring wan0 via 8.8.8.8 for Failure
Aug 14 17:51:07 router wan-failover.sh: WAN0 Failover Monitor - Monitoring wan1 via 8.8.4.4 for FailureUsing:
Code:
ip route add 8.8.4.4 via $(nvram get wan1_gateway) dev $(nvram get wan1_gw_ifname)Will try 14e when you want me to with the same -- to see if we loop.
Ranger802004
Very Senior Member
I think I have enough info at this point to make a compensation fix for this so you are free to standby so I can update again.
Perfection. Got some people remoted in now, so take your time. Will also be testing the Auto QoS settings at some point. Then perhaps look at selective off/on based on up/down speeds
Assuming you are interested in going there!Cheers!
Ranger802004
Very Senior Member
I will after v1.5.6 because that will require new settings to maintain in configPerfection. Got some people remoted in now, so take your time. Will also be testing the Auto QoS settings at some point. Then perhaps look at selective off/on based on up/down speeds
Cheers!
Ranger802004
Very Senior Member
Are you using VPN Director by any chance with all of your WAN traffic redirected?Perfection. Got some people remoted in now, so take your time. Will also be testing the Auto QoS settings at some point. Then perhaps look at selective off/on based on up/down speeds
Cheers!
No not at all. I do have site to site VPNs (with mine being the server) for a couple remote sites, but not for internet access, just LAN.
Stephen Harrington
Very Senior Member
Since you are hinting there IS an "after 1.5.6" small request for consideration? ...
I've gotten "my" version of your logs going nicely in the Merlin GUI using Scribe / .
But that means your Monitor Mode no longer works, as Scribe has already extracted and moved them from "messages" where it looks.
Any chance in a future version you could have a config option for us to manually select the log location you are tailing for your monitor function?
In my case that would be "wan-failover.log" in the same Scribe directory, /opt/var/log.
That way I could have it appear both in the GUI and also use your Monitor Mode if I needed to.
You could have your auto-locate default as it now so present behaviour doesn't change, but IF there was a manual location set in your config file that would then override?
Alternatively, you could just mandate the name and have "wan-failover.log" as the 1st preferred log option if your script finds it?
Also convenient as it means your logs stay separate ready to go if I need to send them to you (AGAIN).
Ranger802004
Very Senior Member
Where does Scribe move them to after /messages?Since you are hinting there IS an "after 1.5.6" small request for consideration? ...
I've gotten "my" version of your logs going nicely in the Merlin GUI using Scribe / .
View attachment 43536
But that means your Monitor Mode no longer works, as Scribe has already extracted and moved them from "messages" where it looks.
Any chance in a future version you could have a config option for us to manually select the log location you are tailing for your monitor function?
In my case that would be "wan-failover.log" in the same Scribe directory, /opt/var/log.
That way I could have it appear both in the GUI and also use your Monitor Mode if I needed to.
You could have your auto-locate default as it now so present behaviour doesn't change, but IF there was a manual location set in your config file that would then override?
Alternatively, you could just mandate the name and have "wan-failover.log" as the 1st preferred log option if your script finds it?
Also convenient as it means your logs stay separate ready to go if I need to send them to you (AGAIN).
Ranger802004
Very Senior Member
No worries, just trying to figure out why some routers have trouble with the IP Rules and others don't. My friend in town who is running Merlin as well is going to loan me his AX86U to test around with and see if I can come up with some answers on that.
Ranger802004
Very Senior Member
Republished v1.5.6-beta14f, I changed it where it will determine which IP Rule or route is successful at achieving a ping to the Target IP starting with 1. IP Rule w/ Outbound Interface, 2. IP Rule w/o Outbound Interface, 3. IP Route
Safe to test now for the looping and WAN1 detection for myself you figure?
Ranger802004
Very Senior Member
Yes
Looks good. I see what you have done. Great work!
Code:
Aug 14 23:20:00 router wan-failover.sh: System Check - Version: v1.5.6-beta14f
Aug 14 23:20:00 router wan-failover.sh: Debug - Firmware: 386.7
Aug 14 23:20:00 router wan-failover.sh: System Check - IPRoute Version: 5.11.0
Aug 14 23:20:00 router wan-failover.sh: Debug - JFFS custom scripts and configs: 1
Aug 14 23:20:00 router wan-failover.sh: Debug - Checking Alias in /jffs/configs/profile.add
Aug 14 23:20:00 router wan-failover.sh: Debug - Checking for Configuration File: /jffs/configs/wan-failover.conf
Aug 14 23:20:00 router wan-failover.sh: Debug - Function: setvariables
Aug 14 23:20:00 router wan-failover.sh: Debug - Reading /jffs/configs/wan-failover.conf
Aug 14 23:20:00 router wan-failover.sh: Debug - Checking for missing configuration options
Aug 14 23:20:00 router wan-failover.sh: Debug - System Uptime: 258627 Seconds
Aug 14 23:20:00 router wan-failover.sh: Debug - Checking if wan-failover.sh restarted
Aug 14 23:20:00 router wan-failover.sh: Debug - ***Checking if PIDs array is null*** Process ID(s): 30206 30208
Aug 14 23:20:00 router wan-failover.sh: Restart - Successfully Restarted wan-failover.sh Process ID(s): 30206 30208
Aug 14 23:20:01 router wan-failover.sh: Debug - Reading /jffs/configs/wan-failover.conf
Aug 14 23:20:01 router wan-failover.sh: Debug - Function: debuglog
Aug 14 23:20:01 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:01 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:01 router wan-failover.sh: Debug - Function: wanstatus
Aug 14 23:20:01 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:01 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:01 router wan-failover.sh: Debug - System Uptime: 258627 Seconds
Aug 14 23:20:01 router wan-failover.sh: Debug - Boot Delay Timer: 5 Seconds
Aug 14 23:20:01 router wan-failover.sh: Debug - Setting parameters for wan0
Aug 14 23:20:01 router wan-failover.sh: WAN Status - wan0 enabled
Aug 14 23:20:01 router wan-failover.sh: Debug - Checking wan0 State
Aug 14 23:20:01 router wan-failover.sh: Debug - Checking wan0 for null IP or Gateway
Aug 14 23:20:01 router wan-failover.sh: Debug - Checking wan0 for Default Route in 100
Aug 14 23:20:01 router wan-failover.sh: Debug - Recursive Ping Check: 3
Aug 14 23:20:01 router wan-failover.sh: Debug - Checking wan0 for IP Rule to 8.8.8.8
Aug 14 23:20:01 router wan-failover.sh: WAN Status - Adding IP Rule for 8.8.8.8 to monitor wan0
Aug 14 23:20:01 router wan-failover.sh: WAN Status - Added IP Rule for 8.8.8.8 to monitor wan0
Aug 14 23:20:01 router wan-failover.sh: Debug - Checking wan0 for packet loss via 8.8.8.8 - Attempt: 1
Aug 14 23:20:04 router wan-failover.sh: Debug - wan0 Packet Loss: 0%
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan0 for Default Route in 100
Aug 14 23:20:04 router wan-failover.sh: Debug - wan0 Ping Path: 1
Aug 14 23:20:04 router wan-failover.sh: WAN Status - wan0 has 0% packet loss
Aug 14 23:20:04 router wan-failover.sh: Debug - wan0 Status: CONNECTED
Aug 14 23:20:04 router wan-failover.sh: Debug - Function: setwanstatus
Aug 14 23:20:04 router wan-failover.sh: Debug - Setting parameters for wan1
Aug 14 23:20:04 router wan-failover.sh: WAN Status - wan1 enabled
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan1 State
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan1 for null IP or Gateway
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan1 for Default Route in 200
Aug 14 23:20:04 router wan-failover.sh: Debug - Recursive Ping Check: 3
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan1 for IP Rule to 8.8.4.4
Aug 14 23:20:04 router wan-failover.sh: WAN Status - Adding IP Rule for 8.8.4.4 to monitor wan1
Aug 14 23:20:04 router wan-failover.sh: WAN Status - Added IP Rule for 8.8.4.4 to monitor wan1
Aug 14 23:20:04 router wan-failover.sh: Debug - Checking wan1 for packet loss via 8.8.4.4 - Attempt: 1
Aug 14 23:20:08 router wan-failover.sh: Debug - wan1 Packet Loss: 100%
Aug 14 23:20:08 router wan-failover.sh: Debug - Checking wan1 for Default Route in 200
Aug 14 23:20:08 router wan-failover.sh: WAN Status - Adding route for 8.8.4.4 via xxx.xxx.200.1 dev eth1
Aug 14 23:20:08 router wan-failover.sh: WAN Status - Added route for 8.8.4.4 via xxx.xxx.200.1 dev eth1
Aug 14 23:20:11 router wan-failover.sh: Debug - wan1 Packet Loss: 0%
Aug 14 23:20:11 router wan-failover.sh: WAN Status - ***Warning*** Compatibility issues with 8.8.4.4 may occur with adding route via xxx.xxx.200.1 dev eth1
Aug 14 23:20:11 router wan-failover.sh: Debug - wan1 Ping Path: 3
Aug 14 23:20:11 router wan-failover.sh: WAN Status - wan1 has 0% packet loss
Aug 14 23:20:11 router wan-failover.sh: Debug - wan1 Status: CONNECTED
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: setwanstatus
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: debuglog
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:11 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: switchdns
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:11 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:11 router wan-failover.sh: Debug - Setting WAN0 Status for DNS Switch
Aug 14 23:20:11 router wan-failover.sh: Debug - Manual DNS Settings for wan0
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Adding wan0 DNS1 Server: 1.1.1.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Added wan0 DNS1 Server: 1.1.1.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Adding wan0 DNS2 Server: 1.0.0.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Added wan0 DNS2 Server: 1.0.0.1
Aug 14 23:20:11 router wan-failover.sh: Debug - Setting WAN1 Status for DNS Switch
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Removing wan1 DNS1 Server: 1.1.1.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Removed wan1 DNS1 Server: 1.1.1.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Removing wan1 DNS2 Server: 1.0.0.1
Aug 14 23:20:11 router wan-failover.sh: DNS Switch - Removed wan1 DNS2 Server: 1.0.0.1
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: checkiprules
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:11 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:11 router wan-failover.sh: Debug - Setting WAN0 Status for Check IP Rules
Aug 14 23:20:11 router wan-failover.sh: Debug - wan0 NAT Enabled: 1
Aug 14 23:20:11 router wan-failover.sh: Debug - Setting WAN0 Status for Check IP Rules
Aug 14 23:20:11 router wan-failover.sh: Debug - wan1 NAT Enabled: 1
Aug 14 23:20:11 router wan-failover.sh: Debug - WAN0STATUS: CONNECTED
Aug 14 23:20:11 router wan-failover.sh: Debug - WAN1STATUS: CONNECTED
Aug 14 23:20:11 router wan-failover.sh: Debug - WAN1 is Connected
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: wan0failovermonitor
Aug 14 23:20:11 router wan-failover.sh: Debug - Function: nvramcheck
Aug 14 23:20:11 router wan-failover.sh: Debug - ***NVRAM Check Passed***
Aug 14 23:20:11 router wan-failover.sh: WAN0 Failover Monitor - Monitoring wan0 via 8.8.8.8 for Failure
Aug 14 23:20:11 router wan-failover.sh: WAN0 Failover Monitor - Monitoring wan1 via 8.8.4.4 for FailureCheers on this late Sunday!
Stephen Harrington
Very Senior Member
To wherever one nominates in the custom filter you write, based on existing templates, but in my case same directory as all the other Scribe logs, the not very imaginative:-
Ranger802004
Very Senior Member
The same fix may work for @Ubimo
Ranger802004
Very Senior Member
I'll consider a custom config location for next version.
Similar threads
DomainVPNRouting
Domain VPN Routing v3.0.3 ***Release***
Similar threads
Similar threads
-
-
DUAL WAN Failover version v2.1.2 and router RT-AX88U_PRO
- Started by dexu
- Replies: 0
-
-
Wan Failover Script is reported constant switching
- Started by routersecskisthedude
- Replies: 5
-
amtm The amtm update command does not work when using 2x WAN.
- Started by dexu
- Replies: 3
-
-
Unbound DHCP DNS same as WAN DNS based on merlin-dns-monitor.sh
- Started by salvo
- Replies: 0
-