and what shows
#ip ro sh cache
?
It might be that you have not arp of some host who respond for icmp and arp's
in case of some recieved icmp redirect packet.
-----Original Message-----
From: "gypsy"<[EMAIL PROTECTED]>
Sent: 05-05-18 05:27:02
To: "Antonio Pinizzotto"<[EMAIL PROTECTED]>
Cc: "[email protected]"<[email protected]>
Subject: Re: [LARTC] problem with the "arp" command (using the pub flag)
Antonio Pinizzotto wrote:
> ___PROBLEM___
>
> The problems is that, sometimes, the second line (the one with the P
> Flag in the "arp -n" output) desappears for some time and then appears
> again... !!?
>
> Note.
> Do you know if it is normal or if it could be a bug in "arp"?
> I didn't verify if, when the second line is not present, the host A
> continues to answer to ARP Request for 192.168.30.130 on eth0.
> In other words I didn't verify if it's just a problem in the output (of
> "arp -n" command) and not in the behaviour.
>
> Antonio
You got Trouble, Antonio!
I've been running for 2+ months with no "disappearing" PUB arps. arp -n
works flawlessly.
Wondering: Could it be a bad NIC or cable?
--
gypsy
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
_______________________________________________
LARTC mailing list
[email protected]
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
