|
Hello,
On Thu, 17 Jul 2003, Stephan Wonczak wrote:
> I have just reproduced the problem again (we got around it last time by
> rebooting lvr8). Here is a snippet of 'tcpdump -e -i eth2 -l arp' from a
> time after the director is back on lvr7:
>
> 16:10:15.916326 0:0:be:a6:50:21 Broadcast arp 60: arp who-has
> lrv.rrz.uni-koeln.de (Broadcast) tell starfire.rrz.Uni-Koeln.DE
Are you sure that at this point 134.95.19.15 (lrv)
is not configured on some interface in lvr8? May be not on
eth2, may be on another interface? Please, do 'ip a' and save
the output at that point, showing only eth2 is absolutely not enough.
Do you know that Linux can reply to requests coming from eth2
even if the local IP is configured on dummy0, for example?
> 16:10:15.916360 0:2:b3:be:8a:a6 0:0:be:a6:50:21 arp 42: arp reply
> lrv.rrz.uni-koeln.de is-at 0:2:b3:be:8a:a6
Regards
--
Julian Anastasov <ja@xxxxxx>
|
