by We've had an odd situation that seems to highlight different arp behavior
between Solaris 2.5 and 2.3. We've got a PC that changes its ethernet address
(not its IP address) when it switches from DOS to Linux (we're trying to debug
this separately), and our 2.3 server has no trouble immediately responding to
the new address but the 2.5 server doesn't. It takes up to two minutes to clue
in and respond correctly. It's like the 2.3 system is updating the arp cache
with every packet that comes in, but the 2.5 system isn't.
Is this as intended or is something odd about our 2.5 machine?
Honestly, of all the things that can break, I thought I could trust arp.
Chip Campbell
Sunnybrook Health Science Centre (U of Toronto)