Recent content by tul918

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...

There is a Cisco SG300 28 port POE+ switch between the router and the WAPS. Everything is wired, no mesh. Anything not on wifi is wired to a patch panel and goes through the SG300. I swapped out an OPNSense firewall for the AX86U Pro. Before that was a AC68U. I've never had this problem...

I've changed back to using the ISP (Windstream) DNS servers. I really don't expect that to make a difference, but taking 3rd part DNS servers out of the equation. Confident this is not an ISP issue. The reset is the quickest means to getting internet back. Like I've said, when the issue is...

The first time this happened I could see a DNS redirect happening. I turned off the wan down redirect then, but I suspect that is still what's happening even though it's turned off. It may be a while before I can start testing again. We lose internet until I can get the router set back up...

Fiber comes into the house via ethernet. No router or modem upstream. No DNS director. WAN DNS set manually on the router to 1.1.1.1 and 8.8.8.8 VPN not enabled. No Pi Hole. I can initiate the issue by unplugging the wan port or rebooting the router. When the router thinks the WAN is down the...

Yes, definitely DNS related. The first time it happened it looked like it was trying to redirect traffic due to the WAN being down. I just can't DNS resolution back on the clients after the router thinks the WAN is down. I've tried static DNS on the clients with no joy. The router itself...

Running 3006.102.4 This has happened in the past when the router has been rebooted. The router has internet, I can ping externally and run speed tests from the router. However, the clients cannot get to the internet. Ultimately I have to do a factory reset and reconfigure the router. I've...