Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?

Submission Summary: 0 pending, 2 declined, 0 accepted (2 total, 0.00% accepted)

Slashdot Deals: Deal of the Day - Pay What You Want for the Learn to Code Bundle, includes AngularJS, Python, HTML5, Ruby, and more. ×

Submission + - Best practices for private IP space management? 1

Chris Snook writes: My company makes embedded routers that are deployed widely, and each needs a few subnets, which do not need to be unique from one device to the next, so we've been using the space broken up into /24 subnets. To avoid colliding with those, we decided to use the range for tunnels between our management servers and the routers in the field, but it turns out our hosting provider uses the space internally. To top it off, our ISP sometimes routes packets through routers with IPs, which makes debugging a headache if development code screws up a route that's meant to go internally. It there a best practice for managing the address space, or are we out of luck once we're interacting with networks beyond our control?

Going the speed of light is bad for your age.