Hacker News Reader

Comment by peterburkimsher | Hacker News Reader

There are actually products that do this kind of power cycling. I'm a happy user of a ResetPlug that fixes my WiFi problems by rebooting the router when the connection is down.

(I don't mean this as a spammy ad, just in case other people have as terrible Internet access as Chunghwa is giving me)

View on HN

TBH you probably need a better WiFi router, not some external device that turns it off and on for you... Can you not at least schedule reboots of your current router? That silly plug is $60! You could have bought a mikrotik wifi router for cheaper than that...

The router is provided by the landlord, who already called out the service people from Chunghwa Telecom to look at it.

They turned it off and on again, and it worked (of course). So they refused to replace it.

And I can't schedule reboots, because it usually fails a few minutes after I start using it when I return to my house (not at a consistent time every day).

Ah that's a bummer. It's a modem/router-combo then. I've never had good experiences with the ISP provided ones...

You should be able to buy your own wifi router and plug it into your router/modem combo. Ideally, you'd then run the combo in bridge mode, but it should work regardless.

should and can, are not the same thing.

Why in the world would is that something you shouldn't do?

>you probably need a better WiFi router. That's the right answer. Last time I rebooted a router or AP: never. Unless there's a power failure they run years on end without intervention (DD-WRT on a Buffalo AP, DD-WRT on Netgear WNR3500's, and a number of managed HP MSM422 & Ubiquiti APs if you are curious).

I think restarting after a single pass through the program is a fairly common technique in real-time systems - I think the computers on the Lunar Modules worked this way. It means that you start from a known state on each iteration, and a further refinement is to allow only forward branches (so 'if', but no loops).

Yup, the aerospace data acquisition system that I've used works this way - each acquisition cycle finishes by resetting the FPGA and coming up from a blank slate.

I shouldn't admit it, but I have some tricky memory leak in a node.js server for my app - I spent an evening trying to find it, but in the end I just added daily restart of an app to cron, and it works beautifully ever since :).

Shouldn't admit it? It's my most recent blog post!

http://designbymobi.us/turn-it-off-and-on-again/

Reply on news.ycombinator.com