On Sat, 31 Dec 2011, Eric Rosenberry wrote:
Under that logic, the .254 IP on the other router is also the broadcast address since it is in a /32 subnet as well...
For laughs I tried to use the highest and lowest address of a class B network as loopback addresses. Some stuff will not work if you choose the highest or lowest address of a classful network, in your case class C.
Either you start logging cases against this so they fix the code, or if you value your time, don't use these addresses (.0.0 and .255.255 on 128.0.0.0-191.255.255.255 and .0 and .255 of 192.0.0.0-223.255.255.255).
I would imagine the same problem exists with .0.0.0 and .255.255.255 in class A space.
-- Mikael Abrahamsson email: swm...@swm.pp.se _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/