ApexRon
Very Senior Member
In my years with Verizon, the seemingly easy task of recognizing when a WAN outage occurred and taking appropriate action fast enough such that the end user awareness was minimal proved to be a daunting task. Then there was the opposite task of knowing when the outage was resolved and reverse the previous action. When I retired in 2010 Verizon was doing an excellent job performing these tasks, though not perfect, through automation. Realize that what I just spoke of was regarding the Verizon internet infrastructure as well as client private connections that traversed multiple, non-Verizon networks.Everything is on the same subnet. I had been experimenting with OPNSense and PFSense. I just don't have the time to devote to messing with either right now. I wanted to simplify back to a home router. Amazon had the Pro's for $100 so I went ahead and got 4 of them. I get enough time working things out in a lab at work. Really just want a simple setup at home so I don't have to come home and "work".
I've been a long time member here, my account was locked so I created a new account. I was really hoping for Merlin to comment on the Wan down redirect. I recall him being active on this forum back in the day. I saw quite a few posts saying it was a known bug that had yet to be fixed. Didn't think this would get down in the weeds like it has. I appreciate all the help, but like I've said before I'm feeling pretty strongly this is a DNS redirect issue. Each time the problem has happened the situation was such that getting the internet back was a priority so I didn't spend more than a few minutes troubleshooting. I'm going to have to spend some more time on my end to flesh this out. Thanks guys
In your situation, automation may be something to consider. Automation to recognize an issue for clients and take appropriate action fast to invoke a backup. Then periodically evaluate status of primary connection and make a determination when to switch back.