[157439] in North American Network Operators' Group
Issues encountered with assigning .0 and .255 as usable addresses?
daemon@ATHENA.MIT.EDU (Paul Zugnoni)
Mon Oct 22 18:09:11 2012
From: Paul Zugnoni <paul.zugnoni@jivesoftware.com>
To: "nanog@nanog.org" <nanog@nanog.org>
Date: Mon, 22 Oct 2012 22:07:50 +0000
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@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 shoul=
d 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 N=
AT pool, or subnets larger than /24). Yet I've run into a commercial IP mgm=
t 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=85. 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.
