Re:Microsoft and Red Hat partner
by X-Istence on Wednesday November 04, 2015 @12:46PM
(#10508223)
I don't see why private IP's in a trace route is necessarily wrong...
Many large providers are numbering their hops with private IP space and routing public space across it because they don't want to waste /30's of public space for each point to point.
Yes, /31 is an option, but there were a lot of edge cases or network gear that didn't support it.
Re:Microsoft and Red Hat partner
by X-Istence on Saturday November 07, 2015 @03:57PM
(#10526198)
Unfortunately IPv6 in cloud deployments is still very much lacking. OpenStack is one of those where IPv6 has only recently become something that is being built into OpenStack.
Many large providers are numbering their hops with private IP space and routing public space across it because they don't want to waste /30's of public space for each point to point.
Yes, /31 is an option, but there were a lot of edge cases or network gear that didn't support it.