Didn’t even need a paperclip.
sunglasses
Judging by my experience, router software probably has memory leaks so it eventually runs out of available memory and stops working properly.
This is more so if you’re using it for something that opens and closes a ton of connections, such as torrenting. In fact maybe 1 or 2 decades ago when those things had less memory the low and mid end quality routers couldn’t handle torrenting directly (so, when the router had to route each new connection, not behind a VPN were its the VPN-server that does it) without dying in a few hours.
Most slow or even no-connection problems I have get solved by restarting the router, though I have my own router and it’s a high-end consumer one (rather that using the one provided by the ISP), so nowadas that kind of problem happens maybe twice a year at most.
On and then off you say?
It temporarily fixed the issues, but then they continued afterwards.
Actually turning the route ON and then OFF again would temporarilly solve a no-connection problem but then it would come back.
You rang?
can’t have connection issues if you have no connection
That’s why many cybersecurity professionals have their house no-tech or low-tech.
That’s why they turned it off at the end.
Sophisticated!
Bonus points if you had to bend a paperclip to push the reset button
I feel like — like myself — none of the technical users of Lemmy would actually like this. For me, my router is a mini PC running Alpine Linux and it’s likely the modem (which is also my own) is having problems with the physical cable connection but if I were using an all-in-one shit box from the ISP there would be no way of knowing.
All this to say, if restarting the router “fixes” things there’s likely a deeper, more unsettling problem happening that’s not being diagnosed.
Came here to say just this. ISP box goes into a Debian board with 10 gigE uplink to my actual switching. I asked if I could replace the XGPON-ONT by SFP+s but Alas the sales agent was rather confused and basically said “why?!”…
For me, it was openwrt bouncing the external interface during a DHCP renewal, even when the IP didn’t change. They still haven’t fixed that. I patch the stupid file every upgrade.
But yeah, at least I could fix it!
I’ve actually got the exact same issue - how did you end up fixing it?
All this to say, if restarting the router “fixes” things there’s likely a deeper, more unsettling problem happening that’s not being diagnosed.
Odds are it’s just some memory leak.
Having to reboot every 2-3 month isn’t too far fetched for these ISP modem/router.
