Re: Arp problems

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



In article <200201140212.g0E2C3CV019812@backfire.WH8.TU-Dresden.De> you wrote:
> The majority of the arp requests is fine:

> 03:08:07.626268 arp who-has 141.30.225.1 tell 141.30.225.254
> 03:08:07.626712 arp reply 141.30.225.1 is-at 0:60:5c:5e:82:d1

> just some show this behaviour.

> Does it make a difference if I've set up with the old (ifconfig, route) tools?
> BTW: The route for eth2 was set up by ifconfig.

It should not make a difference as long as you do not use rules.

I think in your situation, the router is asking the ARP request because an
application/socket bound to the wrong address tries to contact a host in your
upper network. Therefore the auto binding of the local address will not take
place. 

Have a look at the "netstat -tupe" output, right after the arp request. You
will see most likely a established TCP connection or UDP request. You can also
tcpdump for them.

Greetings
Bernd
-
: send the line "unsubscribe linux-net" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Netdev]     [Ethernet Bridging]     [Linux 802.1Q VLAN]     [Linux Wireless]     [Kernel Newbies]     [Security]     [Linux for Hams]     [Netfilter]     [Git]     [Bugtraq]     [Yosemite News and Information]     [MIPS Linux]     [ARM Linux]     [Linux RAID]     [Linux PCI]     [Linux Admin]     [Samba]

  Powered by Linux