Could this be like:Depending on how your internet works - probably a Netwatch script that then modifies VRRP priorities to force the other one to take over Master
The problem with this is, the gateway would always be powered up and pingable even when the internet is down (hurricane knocks out outdoor fiber lines) so this couldn't work. The fix for me would be to ping some known IP that does indicate internet (such as 1.1.1.1 or 8.8.8.8 or the next hop over in the AT&T network).If you have Static IP hand-off, you could try pinging your gateway as netwatch, which shouldn't be pingable if internet was to swap to other router
Yes - exactly why I said it is VERY dependent on your exact setup. Just hard static routing via your provider to 1.1.1.1 should be OK, and change the netwatch script on that. Just don't let that static route propogate to the other router too otherwise clients will not reach 1.1.1.1 when on backup.The problem with this is, the gateway would always be powered up and pingable even when the internet is down (hurricane knocks out outdoor fiber lines) so this couldn't work. The fix for me would be to ping some known IP that does indicate internet (such as 1.1.1.1 or 8.8.8.8 or the next hop over in the AT&T network).If you have Static IP hand-off, you could try pinging your gateway as netwatch, which shouldn't be pingable if internet was to swap to other router