3 ms·
Just FYI - you can't technically carve up a /64 without breaking EUI-64 rules if you're talking about subnets. With that said, you can still technically do jus
by windexh8er 13y ago
Just FYI - you can't technically carve up a /64 without breaking EUI-64 rules if you're talking about subnets.
With that said, you can still technically do just that or just break it up logically. You can have some interesting fun with routing between a few internal hosts. I've had some fun with Quagga on Linode slices in this regard.
- IgorPartola 13y agoI am not suggesting carving up a /64, but rather just allocating a /64 to every customer. Then I can allocate addresses out of the /64 to my own instances. I can further instruct them to not communicate on certain ports with anything outside of my /64. For example, I could tell my DB servers to only serve my /64, etc. I suppose if you are doing something cross data center then you want a larger allocation. Linode currently allocates 1 address per instance I think? It's better than nothing, but really they should do a /64.
- spindritf 13y ago> Then I can allocate addresses out of the /64 to my own instances. I think that would call for a /48† if you're going to split it farther. Handing out /64 per server regardless of how many servers a client has seems just easier to me. One thing they could do due to virtually unlimited number of addresses is to let you keep them (instead of reusing for other customers) even if the servers are offline. You could create servers with IPs known in advance that way. Which actually makes it even more convenient to reserve /48† per customer and then carve out /64 per server. So maybe that's a better route. † or /56 but I don't know if the savings are worth the potential hassle.