Recent content by JohnSmith

I deleted them via SSH, but then I had to go into the "wan-failover.conf" file and blank out the IP address I gave for WAN0. Was looking for an automatic way as part of the script to re-disable it again, which would remove the route created by it. No worries, all back to the way it was...

1. If you add a WAN0 or WAN1 Web GUI IP address, and it doesn't allow you to get to the devices portal, are there any troubleshooting steps to try? 2. If you add a WAN0 or WAN1 Web GUI IP address, and then you want those to be "Disabled" again, how do you revert those back, as the logic only...

On my AX88U, you go under WAN | Internet Connection | WAN Type (My choices are WAN(WAN0) or Ethernet LAN(WAN1), then under "WAN DNS Setting", click the "Assign" button, which gives you options of a "DNS List", which at the bottom is "Manual Setting", which you can assign IP addresses for DNS...

Upgraded RT-AC3100 from V386.11 Final to V386.12 Final via dirty firmware upgrade with no issues.

Update from V2.0.5-beta3 to V2.0.5-Final, appears to be working.

Update from V2.0.3-Final to V2.0.4-beta1, appears to be working.

Upgraded RT-AC3100 from V386.10 Final to V386.11 Final via dirty firmware upgrade with no issues.

Are you sure you have an RT-AX88U as per your signature? There is no V386.10 ASUS Merlin firmware for this product, only V386.8 (which I am on), V388.1 and V388.2. My RT-AC3100 uses V386.10. Are you using an AC68U instead as per "gateway wan1 : 192.168.1.1 (DSL-AC68U-8298)"?

Had my WAN1 go down over night, and since it was not my primary internet, everything continued along no problem. Saw this error in the debug logs, that may just be a typo in the script that a variable is not being added to the text Mar 31 03:54:19 wan-failover: Debug - HTTP Web Access: 0 [[...

More interesting info @Ranger802004 So I hard powered down my ASUS AX88U router (both ISP modems were still powered up), and then powered it back up, and my ISP02 (Secondary WAN) took over as the "Connected" connection, and my ISP01 (Primary WAN) was in "Hot-Standby", but after a minute or so...

Debug Logs sent

Had to add the following command: ip rule add from all iif lo to 8.8.8.8 lookup wan0 priority 100 which once added at SSH command line, it allowed the following ping to occur: ping -I eth0 8.8.8.8 which then the FAILOVER occurred. Once FAILOVER occurred, ran command: ip rule del from all...

Yes, WAN0 packet loss is stuck at 100% via "/jffs/scripts/wan-failover.sh status" script

Full Power OFF of ISP01 modem, wait until FAILOVER occurs, and system logs are complete, and all other addons are working again, then Power ON ISP01 modem to bring it backup, where the ASUS AX88U router shows on the TAB "Network Map | Primary WAN" is in "Hot-Standby", but never changes over...

Testing V2.0.0 Final Dual WAN Script in a Dual WAN FailBack mode: (errors in BOLD) Test01: - ISP01 goes down, ISP02 takes over in FailOver mode - ISP01 comes back up, ISP02 continues to be the main WAN, FailBack does NOT work, as Primary WAN stays as Hot-Standby. - Run the "switchwan" argument...