At my very first IT job I tried this when the facility lost its internet connection. I guess the router didn’t have any kind of battery backup because it cleared all of the settings and didn’t regain contact with the ISP.
It didn’t initially go well for me, but eventually the much more experienced IT contractor clarified that that shouldn’t happen and probably wasn’t my fault, at which point I got some leeway.
The sky above the port was the color of television, tuned to a dead channel
Source. Recommend.
You call me?
Beautiful
I love the Power Glove.
Half of all IT tickets are resolved just be rebooting something. All same for services, routers, firewalls, servers or workstations
Reboot helping is true because i know what’s going on in there.
Is this the famed Levi Hackerman
I just did this yesterday. Its MAC tables had gotten corrupted in a way that the PiHole connection was flapping. It was wacky, direct IP connections were solid, external DNS lookups were working but slow due to the fallback, and internal ones were working sporadically.
Not only! You do it by waiting 60 seconds before turning the router on again! That’s some level of shit because they tried to just turn it off and on quickly and didn’t work!
Some (poorly designed) “passive” devices need about 20 seconds between power cycles to empty their capacitors, that’s why.
Also, press buttons why it’s unplugged.
I know, I work with machines and it’s a common practice to let the capacitors discharge for a good minute before trying to turn the thing on so the device has properly turned off before you try to turn it on again. But I know this because I work with them on a daily basis. If someone sees you as “hackerman” because you fixed the wifi by restarting the router properly, chances are they won’t even understand what a capacitor is.
Cereal Killer personified.
