[atlas] Fwd: Issues encountered with assigning .0 and .255 as usable addresses?
Tore Anderson tore.anderson at redpill-linpro.com
Tue Oct 23 22:02:33 CEST 2012
Here's a suggestion for an Atlas experiment and subsequent RIPE Labs article. Do a ping measurement from all the probes to the .0 and .255 address of the same /24, plus to another control address in the same /24, and compare success rates. It's particularly interesting for me as my own personal home page is accessible at 220.127.116.11 at the moment.., Might also be worth checking it out for IPv6 at the same time (at least the case where the last 64 bits are all zeroes). Tore -------- Opprinnelig melding -------- Emne: Issues encountered with assigning .0 and .255 as usable addresses? Dato: Mon, 22 Oct 2012 22:07:50 +0000 Fra: Paul Zugnoni <paul.zugnoni at jivesoftware.com> Til: nanog at nanog.org <nanog at nanog.org> Curious whether it's commonplace to find systems that automatically regard .0 and .255 IP addresses (ipv4) as src/dst in packets as traffic that should be considered invalid. When you have a pool of assignable addresses, you should expect to see x.x.x.0 and x.x.x.255 in passing traffic (ie. VIP or NAT pool, or subnets larger than /24). Yet I've run into a commercial IP mgmt product and getting reports of M$ ISA proxy that is specifically blocking traffic for an IP ending in .0 or .255. Any experience or recommendations? Besides replace the ISA proxy…. Since it's not mine to replace. Also curious whether there's an RFC recommending against the use of .0 or .255 addresses for this reason.