nanog mailing list archives
Re: 10.0.0
From: John Hawkinson <jhawk () bbnplanet com>
Date: Sat, 31 May 1997 09:53:16 -0400 (EDT)
I've noted several providers, including a couple of better-known ones, using RFC1597 addresses internally. While not a Really Optimal Solution, it does work, and if you find yourself with only a couple of class C's to work with.. I'd probably rather preserve them for my customers, and go with whatever I had to internally, as long as packets still got from A to B. The only services that should be affected by the use of such "bogus" addresses will be traceroute and any routing information passed by the device.
Unfortunately that's not quite true. There are a variety of services which rely on messages received from intermediate hops that would break if the the sending host happened to filter out RFC1918 addresses and a part of the network were using them. Probably the best example is Path MTU Discovery. --jhawk
Current thread:
- 10.0.0 Janet Pippin (May 30)
- Re: 10.0.0 Ehud Gavron (May 30)
- Re: 10.0.0 Jared Mauch (May 30)
- Re: 10.0.0 Paul Ferguson (May 31)
- Re: 10.0.0 Bil Herd (May 31)
- <Possible follow-ups>
- Re: 10.0.0 Dave O'Shea (May 30)
- Re: 10.0.0 Philip J. Nesser II (May 30)
- Re: 10.0.0 Alec H. Peterson (May 31)
- Re: 10.0.0 John Hawkinson (May 31)
- Re: 10.0.0 Philip J. Nesser II (May 30)
- Re: 10.0.0 Danny McPherson (May 31)
- Re: 10.0.0 Daniel Senie (May 31)
- Re: 10.0.0 Dave O'Shea (May 31)
- Re: 10.0.0 Tony Li (May 31)
- Re: 10.0.0 Ehud Gavron (May 30)