On 01/01/2012, at 4:33 PM, Eric Rosenberry wrote: > When pinging the loopback IP's of these devices from the Internet, one > responds as expected (from the IP of the loopback), and the other (.255) > responds from a *different* IP address (one of it's interface IP's rather > than the loopback IP).
Yep, ran into this one a few years ago. Its not just ping, SNMP does it too. TAC support request tool is offline at the moment, so I can't look up the bug ID, but we eventually just made a rule to never use .255/32 for loopbacks (along with .0/31 and .254/31 to avoid Windows users complaining about failed traceroutes…). Rgds, - I. _______________________________________________ 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/
