When the WAN connections reset or go offline - it seems like my LAN connectivity goes wonky. Tonight I had my entire LAN go down, the router was blinking blue - and I can't confirm if the WANs were unavailable or not, because I couldn't get in to the router. Nothing in my LAN was accessible. Couldn't ping local devices or the router itself, from any of my systems. Best I could tell my primary WAN was online (modem had no noticeable error lights)
I have dual WAN, I have done controlled failover and it worked fine. When I click "connect" on the tether option for WAN2 (it's a USB 5g dongle), my entire LAN freezes up. I'm not even trying to use WAN2, just "connect" it so it's available. I've been able to reproduce this multiple times.
I don't expect my LAN to be affected at all by WAN connections being up or down or change at all. Tonight's issue left me blind - I looked at the logs on the router after power cycling it - there was nothing for a long time before the router shows the logs from the restart. So wasn't anything tangible there.
Last night this happened TWICE - after the first one, I decided to post (on Reddit, first, but nothing going on there...) and then later it happened again. For the moment I've unplugged my WAN2 tether and stopped that. It's been okay since then - but it was okay for weeks with the WAN2 tether active before this (except for the initial disconnection, which was wonky but I didn't think it was a big enough deal to bring up at the time)
During these LAN "outages" - it seems like pre-existing connections kinda stay open. it's .. weird. I have some pre-existing web and samba connections to some local LAN that were connected/busy at the time of this disconnection... and those are still working, even though I can no longer ping that same system that I am actively talking to.
I can have .17 ping .2 and .3 and .4 but .1 (router) is nothing, at the same time, .2 can't ping .17 back, or .3 or .4 etc.. and .1 (router) is nothing. The LAN is somehow fractured in a weird way.