North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Maybe I'm misreading this but...

  • From: tvo
  • Date: Fri Oct 16 13:37:54 1998

Doesn't this break MTU path discovery though?



-------
John Fraizer    (tvo)           |    __   _
The System Administrator        |   / /  (_)__  __ ____  __ | The choice
mailto:[email protected]        |  / /__/ / _ \/ // /\ \/ / |  of a GNU
http://www.EnterZone.Net/       | /____/_/_//_/\_,_/ /_/\_\ | Generation
                     A 486 is a terrible thing to waste...

On Wed, 14 Oct 1998, I Am Not An Isp wrote:

> At 05:11 PM 10/14/98 -0400, Barry Shein wrote:
> >
> >The following traceroute seems to indicate, according to ARIN, that
> >someone is running routers for spammers in the IANA Reserved netspace?
> 
> [SNIP]
> 
> >> 8  bs-jackson-gw.customer.alter.net (157.130.65.226)  107 ms  132 ms  96 ms
> >> 9  172.17.80.46 (172.17.80.46)  59 ms  53 ms  44 ms
> >>10  172.21.210.18 (172.21.210.18)  122 ms  96 ms  49 ms
> >>11  209.149.111.17 (209.149.111.17)  53 ms (ttl=118!)  58 ms (ttl=118!)
> 150 ms (ttl=118!)
> 
> >What's going on here?
> 
> Barry, 172.16.0.0/12 is part of RFC1918 space.  There is no prohibition of
> addressing routers with these addresses, and in fact I do not know of a
> router that will route RFC1918 space differently than any other IP address.
>  (Of course, you can put in filters, and many people do, but you can filter
> any addresses exactly the same way.)  This is a perfectly legitimate use of
> RFC1918 space, as long as those hosts expect no connectivity outside their
> own network.  Many people use RFC1918 on WAN links and whatnot to preserve
> their ARIN allocations for "real" hosts.  Read the RFC for more info.
> 
> >        -Barry Shein
> 
> TTFN,
> patrick
> 
> I Am Not An Isp
> www.ianai.net
> "Think of it as evolution in action." - Niven & Pournelle
>