News for hackers. Stuff that matters.
Re:The Twelve Days of Crisis – A Retrospective on Linode’s H... by radialbrain on Friday January 29, 2016 @09:49PM (#11000263)
Slightly related question:

They mention segregating their customers into separate /24s, and consequently having to assign an IP from every one of these subnets to the router for use by the customer as a gateway.

Is there any reason why they couldn't get rid of these by having customers set up a static route to the "primary" IP of the router (migration / configuration issues aside)?

Re:The Twelve Days of Crisis – A Retrospective on Linode’s H... by caf on Friday January 29, 2016 @10:10PM (#11000306)
The static route has to be via a gateway that is on a locally connected subnet.
Re:The Twelve Days of Crisis – A Retrospective on Linode’s H... by radialbrain on Friday January 29, 2016 @10:46PM (#11000387)
You can have a static route to any local device, this is essentially what subnet membership does.

For example, if I have IP 192.168.0.2/24 assigned to eth0, my routing table will have:

  192.168.0.2/24 dev eth0 proto static scope link
I'm free to add a local route to a device outside 192.168.0.2/24 though:

  192.168.10.1 dev eth0 proto static scope link
This just indicates that I should be able to resolve the MAC address associated with 192.168.10.1 through an ARP query, same as other devices on my subnet.