Failover not working (no internet) RT-AC5300

[DukenStein1099]

First post. I still can't get the failover to work (internet) and I'm not sure if it's my config of the script, router or my failover device. If someone could point me in the right direction it would be much appreciated. I am sure I'm doing something stupid because I'm a noob.

Router - RT-AC5300 fw 386.14 Dual Wan enabled, USB Modem enabled Orbic RC400L, Verzion Jetpack, connected to asus usb, tethering enabled on jetpack Installed Ranger's latest script (via amtm). default settings.

When I pull the primary internet connection I can see that the script correctly fails over "I think" from Wan0 to Wan1 (jetpack) but I can't get to the internet. The jetpack works fine if I connect a device to it using wifi so I know the jetpack itself works. It appears the jetpack is recognized in the router and the script fails over to it but why no internet? Is there something additionally I need to be configuring in the script or in the router?

The router has dhcp enabled using 192.168.1.1 The jetpack also has dhcp enabled (should I disable it?) but since it was using the same ip subnet as the rotuer I changed it to use 192.168.10.1. Is that ok for it to be on a different subnet? I'm thinking that my problem has to do with this dhcp config between the two devices but I want to make sure I'm not missing something.

Any thoughts or advice much appreciated..

[Ranger802004]

Do you have debug logs from WAN Failover available? I would recreate this scenario capturing debug logs. Make sure debug logging is enabled under System Logs in the GUI and then run WAN Failover with capture option from the menu and then recreate your test scenario. When done end the capture logs function and collect the file it displays afterwards.

[DukenStein1099]

Ok I will do that when I’m home later and post back

[DukenStein1099]

Finally back from traveling and able to test. I hope I did the logging correctly (noob) and I'm attaching file Nov 3 073114 wan-failover Debug -.txt below. Also, is the "allow failback" supposed to be checked in the asus gui? I was confused in the installation instructions. I tried it both ways but figured it wouldn't affect the failover results either way. Any thoughts/suggestions appreciated. Thanks.

[Ranger802004]

WAN Failover is not taking over for your failover functionality because you haven't disabled all of the ASUS factory failover options as documented in the readme.

Nov 3 07:31:17 wan-failover: WAN Status - ASUS Factory Watchdog: Enabled Nov 3 07:31:17 wan-failover: Debug - Function: wandisabled Nov 3 07:31:17 wan-failover: WAN Failover Disabled - WAN Failover is currently disabled. Review Logs Nov 3 07:31:18 wan-failover: WAN Failover Disabled - USB Device for wan1 is in Ready State but in Cold Standby Nov 3 07:31:18 wan-failover: Debug - Function: cleanup Nov 3 07:31:18 wan-failover: Debug - Setting parameters for wan0 Nov 3 07:31:18 wan-failover: Debug - Setting parameters for wan0 Nov 3 07:31:18 wan-failover: Debug - Checking wan0 for IP Rule to 8.8.8.8 Nov 3 07:31:18 wan-failover: Debug - Checking wan0 for Default Route in 100 Nov 3 07:31:18 wan-failover: Debug - Setting parameters for wan1 Nov 3 07:31:18 wan-failover: Debug - Setting parameters for wan1 Nov 3 07:31:19 wan-failover: Debug - Checking wan1 for IP Rule to 8.8.4.4 Nov 3 07:31:19 wan-failover: Debug - Checking wan1 for Default Route in 200 Nov 3 07:31:19 wan-failover: Debug - Checking for Lock File: /var/lock/wan-failover.lock Nov 3 07:31:19 wan-failover: Cleanup - Deleting /var/lock/wan-failover.lock Nov 3 07:31:19 wan-failover: Cleanup - Deleted /var/lock/wan-failover.lock

[DukenStein1099]

I figured I was doing something dumb. I will go back and review the readme and update results Thanks!

[DukenStein1099]

I'm sorry if I am asking a really obvious question but where do I "disable factory failover"? I see this in the readme file: Requirements:

• ASUS Merlin Firmware v386.5 or higher (yes)
• JFFS custom scripts and configs Enabled (yes)
• Dual WAN Enabled (yes)
• ASUS Factory Failover Disabled (Network Monitoring Options, Allow Failback Option under WAN > Dual WAN) (???)

I'm not sure what the last one is. I don't see anywhere for "Network Monitoring Options".

Under the Wan/Dual Wan tab I have Dual Wan enabled and then there is a choice for Dual Wan Mode (Failover or Load Balancing, I have Failover). There is then a checkbox for whether you want to Allow Failback. I have tried both checked and unchecked without success. I have also tried both checking/unchecking DNS query/Ping, also without success. Is there somewhere else where I should be "disabling the factory failover". Attaching pic.

[Ranger802004]

• ASUS Factory Failover Disabled (Network Monitoring Options, Allow Failback Option under WAN > Dual WAN) (???)

ASUS Factory Failover Disabled (Network Monitoring Options, Allow Failback Option under WAN > Dual WAN) (???)

[DukenStein1099]

ok thanks. I will try that later this afternoon. I did try it this morning and I wasn't able to access the internet but maybe now it's a different problem and it is failing over correctly but it's something else. I will run another capture log later and see what it says.

[Ranger802004]

ok thanks. I will try that later this afternoon. I did try it this morning and I wasn't able to access the internet but maybe now it's a different problem and it is failing over correctly but it's something else. I will run another capture log later and see what it says.

Any updates?

[DukenStein1099]

yes sorry was just able to do it. Here's the latest capture with the settings unchecked pics and file attached. 11072024.wan-failover.Debug.-.txt Thoughts?

[Ranger802004]

How is your Primary WAN connected?

Did you unplug it?

[DukenStein1099]

The Primary Wan is connected via ethernet to the wan port on the router. For the test I initially left it plugged in, started capture in the script, then unplugged the the primary to simulate a primary failure. You can see from my pics that the router shows the primary wan as unplugged/disconnected and it shows the secondary as connected. I'm not sure what the capture is saying because I'm unsure how to interpret it. From the asus router gui it appears to be failing over but not grabbing an ip from the jetpack.

Do I have the router settings configured properly now?

[Ranger802004]

Is it possible for you to test without physically unplugging your WAN0? Maybe there is a connection to your Primary ISP you can disrupt to test? When you unplug it, your router is still trying to switch to the WAN1 for some reason and causing some issues with WAN Failover switching to WAN1.

[DukenStein1099]

sure i will do it right now and post back

[DukenStein1099]

ok I pulled the power on my fios nic and left the physical ethernet connection plugged into the asus router. That brought down the internet connection but left all physical cables plugged into the router. As you can see from the pic it says "network cable unplugged" but nothing is unplugged from the router, just the main fios power cable. The router gui says it has switch to wan 1 but it still doesn't show any wan ip/internet. I am also attaching the capture log. Thanks. 11082024.wan-failover.Debug.-.txt

[DukenStein1099]

are you able to tell from the logs whether the script appears to be working? Is it failing over? Trying to narrow down whether it's the configuration of the jetpack pulling an ip or if I'm not even getting that far. Thanks

[Ranger802004]

are you able to tell from the logs whether the script appears to be working? Is it failing over? Trying to narrow down whether it's the configuration of the jetpack pulling an ip or if I'm not even getting that far. Thanks

It's behaving normal as if WAN0 is unplugged like you are showing in your GUI screenshot. Your FIOS is your Primary WAN I assume? Something triggered it to show as unplugged if so which is something done by the firmware not the script, WAN Failover just takes actions based on the data it receives. Below is the debug information received when first launched.

Nov 8 16:17:09 wan-failover: Debug - JFFS custom scripts and configs: 1 Nov 8 16:17:09 wan-failover: Debug - Checking Alias in /jffs/configs/profile.add Nov 8 16:17:09 wan-failover: Debug - Checking for Configuration File: /jffs/configs/wan-failover.conf Nov 8 16:17:09 wan-failover: Debug - Function: update Nov 8 16:17:11 wan-failover: wan-failover is up to date - Version: v2.1.2 Nov 8 16:17:11 wan-failover: System Check - Process Priority: 0 Nov 8 16:17:11 wan-failover: Debug - Function: setvariables Nov 8 16:17:11 wan-failover: Debug - Checking for missing configuration options Nov 8 16:17:11 wan-failover: Debug - Reading /jffs/configs/wan-failover.conf Nov 8 16:17:16 wan-failover: Debug - Function: debuglog Nov 8 16:17:21 wan-failover: Debug - Model: RT-AC5300 Nov 8 16:17:21 wan-failover: Debug - Product ID: RT-AC5300 Nov 8 16:17:21 wan-failover: Debug - Build Name: RT-AC5300 Nov 8 16:17:21 wan-failover: Debug - Firmware: 386.14 Nov 8 16:17:21 wan-failover: Debug - IPRoute Version: ss150210 Nov 8 16:17:21 wan-failover: Debug - WAN Capability: wan usb lan Nov 8 16:17:21 wan-failover: Debug - Dual WAN Mode: fo Nov 8 16:17:21 wan-failover: Debug - Load Balance Ratio: 3:1 Nov 8 16:17:21 wan-failover: Debug - Dual WAN Interfaces: wan usb Nov 8 16:17:21 wan-failover: Debug - ASUS Factory Watchdog: 0 Nov 8 16:17:21 wan-failover: Debug - ASUS Factory DNS Probe: 0 Nov 8 16:17:21 wan-failover: Debug - JFFS custom scripts and configs: 1 Nov 8 16:17:21 wan-failover: Debug - HTTP Web Access: 0 Nov 8 16:17:21 wan-failover: Debug - Firewall Enabled: 1 Nov 8 16:17:21 wan-failover: Debug - IPv6 Firewall Enabled: 0 Nov 8 16:17:21 wan-failover: Debug - LEDs Disabled: 0 Nov 8 16:17:21 wan-failover: Debug - QoS Enabled: 0 Nov 8 16:17:21 wan-failover: Debug - DDNS Enabled: 1 Nov 8 16:17:21 wan-failover: Debug - DDNS Hostname: ryanboyscloud.myddns.me Nov 8 16:17:21 wan-failover: Debug - LAN Hostname: RT-AC5300-72B0 Nov 8 16:17:21 wan-failover: Debug - WAN IPv6 Service: disabled Nov 8 16:17:21 wan-failover: Debug - WAN IPv6 Address: Nov 8 16:17:21 wan-failover: Debug - Process Priority: 0 Nov 8 16:17:21 wan-failover: Debug - Default Route: 192.168.10.1 dev usb0 proto kernel scope link 192.168.1.0/24 dev br0 proto kernel scope link src 192.168.1.1 192.168.10.0/24 dev usb0 proto kernel scope link src 192.168.10.127 127.0.0.0/8 dev lo scope link default via 192.168.10.1 dev usb0 Nov 8 16:17:21 wan-failover: Debug - OpenVPN Server Instances Enabled: Nov 8 16:17:21 wan-failover: Debug - Setting parameters for wan0 Nov 8 16:17:22 wan-failover: Debug - wan0 Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan0 Routing Table Default Route: Nov 8 16:17:22 wan-failover: Debug - wan0 Ping Path: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 Target IP Rule: Nov 8 16:17:22 wan-failover: Debug - wan0 Target IP Route: Nov 8 16:17:22 wan-failover: Debug - wan0 Reverse Path Filter: 1 Nov 8 16:17:22 wan-failover: Debug - wan0 IP Address: 0.0.0.0 Nov 8 16:17:22 wan-failover: Debug - wan0 Real IP Address: Nov 8 16:17:22 wan-failover: Debug - wan0 Real IP Address State: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 Gateway IP: 0.0.0.0 Nov 8 16:17:22 wan-failover: Debug - wan0 Gateway Interface: eth0 Nov 8 16:17:22 wan-failover: Debug - wan0 Interface: eth0 Nov 8 16:17:22 wan-failover: Debug - wan0 Automatic ISP DNS Enabled: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 Automatic ISP DNS Servers: 1.1.1.1 1.0.0.1 Nov 8 16:17:22 wan-failover: Debug - wan0 Manual DNS Server 1: 1.1.1.1 Nov 8 16:17:22 wan-failover: Debug - wan0 Manual DNS Server 2: 1.0.0.1 Nov 8 16:17:22 wan-failover: Debug - wan0 State: 4 Nov 8 16:17:22 wan-failover: Debug - wan0 Aux State: 1 Nov 8 16:17:22 wan-failover: Debug - wan0 Sb State: 3 Nov 8 16:17:22 wan-failover: Debug - wan0 Primary Status: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 USB Modem Status: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 UPnP Enabled: 0 Nov 8 16:17:22 wan-failover: Debug - wan0 NAT Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan0 Target IP Address: 8.8.8.8 Nov 8 16:17:22 wan-failover: Debug - wan0 Routing Table: 100 Nov 8 16:17:22 wan-failover: Debug - wan0 IP Rule Priority: 100 Nov 8 16:17:22 wan-failover: Debug - wan0 Mark: 0x80000000 Nov 8 16:17:22 wan-failover: Debug - wan0 Mask: 0xf0000000 Nov 8 16:17:22 wan-failover: Debug - wan0 From WAN Priority: 200 Nov 8 16:17:22 wan-failover: Debug - wan0 To WAN Priority: 400 Nov 8 16:17:22 wan-failover: Debug - wan0 OVPN WAN Priority: 100 Nov 8 16:17:22 wan-failover: Debug - Setting parameters for wan1 Nov 8 16:17:22 wan-failover: Debug - wan1 Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 Routing Table Default Route: Nov 8 16:17:22 wan-failover: Debug - wan1 Ping Path: 0 Nov 8 16:17:22 wan-failover: Debug - wan1 Target IP Rule: Nov 8 16:17:22 wan-failover: Debug - wan1 Target IP Route: Nov 8 16:17:22 wan-failover: Debug - wan1 Reverse Path Filter: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 IP Address: 192.168.10.127 Nov 8 16:17:22 wan-failover: Debug - wan1 Real IP Address: 174.206.226.128 Nov 8 16:17:22 wan-failover: Debug - wan1 Real IP Address State: 2 Nov 8 16:17:22 wan-failover: Debug - wan1 Gateway IP: 192.168.10.1 Nov 8 16:17:22 wan-failover: Debug - wan1 Gateway Interface: usb0 Nov 8 16:17:22 wan-failover: Debug - wan1 Interface: usb0 Nov 8 16:17:22 wan-failover: Debug - wan1 Automatic ISP DNS Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 Automatic ISP DNS Servers: 192.168.10.1 Nov 8 16:17:22 wan-failover: Debug - wan1 Manual DNS Server 1: Nov 8 16:17:22 wan-failover: Debug - wan1 Manual DNS Server 2: Nov 8 16:17:22 wan-failover: Debug - wan1 State: 2 Nov 8 16:17:22 wan-failover: Debug - wan1 Aux State: 0 Nov 8 16:17:22 wan-failover: Debug - wan1 Sb State: 0 Nov 8 16:17:22 wan-failover: Debug - wan1 Primary Status: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 USB Modem Status: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 UPnP Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 NAT Enabled: 1 Nov 8 16:17:22 wan-failover: Debug - wan1 Target IP Address: 8.8.4.4 Nov 8 16:17:22 wan-failover: Debug - wan1 Routing Table: 200 Nov 8 16:17:22 wan-failover: Debug - wan1 IP Rule Priority: 100 Nov 8 16:17:22 wan-failover: Debug - wan1 Mark: 0x90000000 Nov 8 16:17:22 wan-failover: Debug - wan1 Mask: 0xf0000000 Nov 8 16:17:22 wan-failover: Debug - wan1 From WAN Priority: 200 Nov 8 16:17:22 wan-failover: Debug - wan1 To WAN Priority: 400 Nov 8 16:17:22 wan-failover: Debug - wan1 OVPN WAN Priority: 200

[DukenStein1099]

yes fios is primary. So does that mean the script is working? Failing over to secondary? I'm not sure from the logs, I still don't understand it all. If the script is failing over correctly, then I'll start working on figuring out why the jetpack isn't pulling an ip. I just want to double check whether the script is failing over correctly.

[Ranger802004]

It looks like it's getting an IP but the problem is your WAN0 is showing disconnected. Do you have a faulty ethernet cable plugged up for WAN0 by any chance? I have seen this before.

[DukenStein1099]

I will check the cables and try bringing the internet connection down using a different method but wouldn't the failover work the same even if a cable was unplugged since the internet is still "down"?

[Ranger802004]

It shouldn't show as unplugged unless it physically sees the cable disconnect from the router.

[DukenStein1099]

ok I am going to try and figure out bouncing the internet later without it saying cable unplugged

[Ranger802004]

Any updates on your issue?

[DukenStein1099]

I haven't been able to successfully drop the internet connection without it saying unplugged but I have another idea I am going to try this afternoon. Will update. Thanks for checking back