This will be included in v1.5.7-beta3 for testing, I have the code written and will update soon.I think, I found an issue during install:
My primary WAN0 is a PPPoE connection, my secondary WAN1 is a LTE USB-Stick.
WAN1 is in Cold-Standby:
View attachment 44334
During install, I see, that the script thinks WAN1 has 0.0.0.0
ASUSWRT-Merlin RT-AC86U 386.7_2 Sun Jul 24 21:39:14 UTC 2022 [email protected]:/tmp/home/root# /usr/sbin/curl -s "https://raw.githubusercontent.com/Ranger802004/asusmerlin/main/wan-failover.sh" -o "/jffs/scripts/wan-failover.sh" && chmod 755 /jffs/scripts/wan-failover.sh && sh /jffs/scripts/wan- failover.sh install wan-failover.sh - Install Mode Press any key to continue to install...Administration > System > Enable JFFS custom scripts and configs is enabled... Creating /jffs/configs/wan-failover.conf... /jffs/configs/wan-failover.conf created. Setting Custom Variables... ***WAN Target IP Addresses will be routed via WAN Gateway dev WAN Interface*** Configure WAN0 Target IP Address - Will be routed via 18.104.22.168 dev ppp0: 22.214.171.124 Configure WAN1 Target IP Address - Will be routed via 0.0.0.0 dev eth7:
WAN1 should have 192.168.8.1 in Hot-Standby.
Is it possible, that the script fires up WAN1 before install?
The script should put WAN1 in hot-standby in order to get the correct route-IP.