|
North American Network Operators Group Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical Re: Qwest/forthelife.net rfc1918 goodness
On Sun, 10 Dec 2000, Mark Mentovai wrote: > I used to think that this was wrong also, and I would never build a network > like that, but aside from making for ugly traceroutes, there's really > nothing wrong with it. RFC 1918 doesn't address this issue directly, but > it's pretty clear that the routers in question don't require network access > beyond the scope of their enterprise, so they are candidates for being > assigned addresses out of private space. The general public doesn't need to There are a few other points. Routers tend to have multiple interfaces. Just because a router sends packets in a traceroute with a private IP source address doesn't mean the router isn't accessible from the internet via a public address on some other interface...just that interface with that address isn't, and most likely doesn't need to be. Some routers neatly accomodate this by allowing you to specify the IP address they'll use for all locally sourced packets. ---------------------------------------------------------------------- Jon Lewis *[email protected]*| I route System Administrator | therefore you are Atlantic Net | _________ http://www.lewis.org/~jlewis/pgp for PGP public key_________
|