WAN led blinks now why?

MylesL

I've had three different Zyxel routers the last few years from our isp and the WAN led has always been solid green when working and red when misconfigured; its always flashed when first connecting/booting up then solid. But the for a nu.ber of months now the service here has been manipulated in ways that have made a handful of separate issues and the reason for this is just to get some help with this light. Our ISP assigns our public IP and its assigned by I guess their own DHCP server. The reason I mention this is because a number of online sources including zyxel sites seem to not be as clear on the reason for flashing and or solid indicators and more specifically in regards to the method in which the IP is given to it and whether or not its static or dynamic assigned by an ISP. Which makes sense because a number of others show the WAN led/globe led to signify the router having or not having an ip address and connection via that ip. I can't think of how it said it. I just know it didn't sound as simple or straightforward just then in my explanation of what the other sources online said about the WAN led and/or IP connectivity led. Something like that.

Sorry for the length. But I need to detail a bit more personal stuff. Theres a weirdo hacker in the family and he hasn't stopped it since he got his first iPhone in middle school. A decade later and its scary. But he moved to his own apartment last summer and that caused his previous little hack had to be changed to some other method/configuration. I'm over 95% certain based on the issues and errors etc over this last year figuring out these new changes that its some kind of transparent proxy. When he lived here he would use open wifi networks to do something and would make their signals really weak like it was from the house across the road. Well passed the distance a 2.4Ghz signal would travel. And I've noticed just about as long that there's a hidden ip on the network of 10.0.0.1 and 10.0.0.2 with our visible and known wifi network at 192.168.1.0/24. I knew it (10.0.0.1) was heavily integral to his weird little setup because after I changed the routers IP from 192.168.1.1 to 10.0.0.1 it completely collapsed the entire network the moment i clicked confirm, and the router became unreachable and required being reconfigration by the isp to get up and running again.