Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

FYI: Linode says that most people can fix this by enabling "Network Helper." You'll then likely need to reboot your server. It worked for me!

https://www.linode.com/docs/guides/network-helper/#individua...



My Newark node was down for over six hours, this is how I fixed it. Uptime on the VPS had been over a year before this (don't remember why it was rebooted a year ago). Like others here said, I did not greet the news of Akamai buying them with joy, and things like this starting seem to bare my initial impressions out.


this.... replaces the use of DHCP with a static file rewriter on boot, OK, why is this recommended in general, should we expect DHCP to have ongoing issues that their "network helper" would not ?


For the vast majority of people, a Linode is just a virtual server that sits on a static IP like a fat toad.

This network helper just assigns that static IP instead of assuming DHCP will find it.

You could turn it off later I guess.


Yeah, we’ve only reallocated an IP address once (in the past week, as it happens), but that was an exception. Our servers are redeployable and backed up, but they’re not really ephemeral. So they just have their IP “forever”. I think the oldest virtual server we’ve had was deleted when it was almost 3 years old.


Thank you! this worked for me too. I was totally down, went in and enabled Auto Configure Networking per your link, and then rebooted.


Most of my Linodes are still accessible, but this has worked for the two that went down so far.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: