On Tue, 2013-08-06 at 11:33 -0400, James Knott wrote:
Greg Freemyer wrote:
Thanks James. For my clarity, is this right?
That is correct. The addresses listed in RFC1918 can be routed internally, but not onto the public Internet. In fact my ISP uses addresses in the 10.x.y.z range within their network. The 169.254 range is called "link local" and cannot be routed, even locally. It's purpose is to allow for file sharing etc. on a local network without having to configure IP addresses.
Just to clarify only the part of internet routing you mentioned (separated from routing inside of organizations[so-called enterprise routing], and I haven't read the original email of the problem) as someone who works for an ISP, RFC1918 ranges are not routable over the internet because there is no route for any super subnets including those ranges on the internet. 4.4.4.2 is routed to Level3's network because they advertises 4.0.0.0/8 to the internet (to their peering ISPs) and it's exhaustively distributed all over the world including our border routers. Also there is no default route 0.0.0.0/0 on the internet so if you send a packet destined to like 192.168.1.1 to your ISP's internet circuit, there is no way for their device to forward that packet to forward to. So it would be discarded. Not because your ISP is identifying it as an IP in private ranges. Just no route. Toshi -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org