|
Hi Julian!
On Thu, 17 Jul 2003, Julian Anastasov wrote:
> On Thu, 17 Jul 2003, Stephan Wonczak wrote:
>
> > in this case. What do we look at next?
>
> Linux can generate ARP reply in many cases:
> 1. There is Local IP configured (no matter the device state)
> ip a
I already gave that one, but here is the output for both machines again:
[root@lvr7 root]# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:06:5b:f0:f4:c4 brd ff:ff:ff:ff:ff:ff
inet 192.168.20.7/24 brd 192.168.20.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
link/ether 00:06:5b:f0:f4:c5 brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:b3:be:8a:9e brd ff:ff:ff:ff:ff:ff
inet 134.95.19.105/24 brd 134.95.19.255 scope global eth2
inet 192.168.19.7/24 brd 192.168.19.255 scope global eth2:3
inet 134.95.19.15/24 brd 134.95.19.255 scope global secondary eth2:0
inet 192.168.19.254/24 brd 192.168.19.255 scope global secondary
eth2:3:0
inet 134.95.19.54/24 brd 134.95.19.255 scope global secondary eth2:1
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
link/ether 00:02:b3:be:8a:9f brd ff:ff:ff:ff:ff:ff
[root@lvr8 conf]# ip a
1: lo: <LOOPBACK,UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 brd 127.255.255.255 scope host lo
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:06:5b:f0:f4:c9 brd ff:ff:ff:ff:ff:ff
inet 192.168.20.8/24 brd 192.168.20.255 scope global eth0
3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
link/ether 00:06:5b:f0:f4:ca brd ff:ff:ff:ff:ff:ff
4: eth2: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 100
link/ether 00:02:b3:be:8a:a6 brd ff:ff:ff:ff:ff:ff
inet 134.95.19.106/24 brd 134.95.19.255 scope global eth2
inet 192.168.19.8/24 brd 134.95.19.255 scope global eth2:3
inet 134.95.19.111/24 brd 134.95.19.255 scope global secondary eth2:4
inet 134.95.19.58/24 brd 134.95.19.255 scope global secondary eth2:0
5: eth3: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 100
link/ether 00:02:b3:be:8a:a7 brd ff:ff:ff:ff:ff:ff
(To recap: lvr7 is the director, lvr8 wrongly answers ARP requests)
> 2. There is /proc/sys/net/ipv4/conf/XXX/proxy_arp enabled
> cat */conf/proxy_arp
[root@lvr7 root]# for f in `ls /proc/sys/net/ipv4/conf/*/proxy_arp` ; do
echo -en $f' \t' ; cat $f ; done
/proc/sys/net/ipv4/conf/all/proxy_arp 0
/proc/sys/net/ipv4/conf/default/proxy_arp 0
/proc/sys/net/ipv4/conf/eth0/proxy_arp 0
/proc/sys/net/ipv4/conf/eth2/proxy_arp 0
/proc/sys/net/ipv4/conf/lo/proxy_arp 0
[root@lvr8 conf]# for f in `ls /proc/sys/net/ipv4/conf/*/proxy_arp` ; do
echo -en $f' \t' ; cat $f ; done
/proc/sys/net/ipv4/conf/all/proxy_arp 0
/proc/sys/net/ipv4/conf/default/proxy_arp 0
/proc/sys/net/ipv4/conf/eth0/proxy_arp 0
/proc/sys/net/ipv4/conf/eth2/proxy_arp 0
/proc/sys/net/ipv4/conf/lo/proxy_arp 0
> Having all/proxy_arp=1 is enough to break everything
Hmm, this does not seem to be the case here.
> 3. There is static ARP entry for the Local IP
> arp -an
[root@lvr7 root]# arp -an
? (134.95.19.54) auf 00:02:B3:BE:8A:9E [ether] PERM auf eth2
? (134.95.19.30) auf 08:00:20:A1:4C:FE [ether] auf eth2
? (134.95.19.27) auf 08:00:20:9A:9E:C4 [ether] auf eth2
? (134.95.19.106) auf 00:02:B3:BE:8A:A6 [ether] auf eth2
? (192.168.19.254) auf 00:02:B3:BE:8A:9E [ether] PERM auf eth2
? (192.168.19.5) auf 00:03:47:73:0E:92 [ether] auf eth2
? (134.95.19.1) auf 00:0B:60:AC:39:8A [ether] auf eth2
? (192.168.19.6) auf 00:03:47:73:0E:94 [ether] auf eth2
? (134.95.19.42) auf 00:03:47:9A:53:7D [ether] auf eth2
? (192.168.20.8) auf 00:06:5B:F0:F4:C9 [ether] auf eth0
? (134.95.19.15) auf 00:02:B3:BE:8A:9E [ether] PERM auf eth2
[root@lvr8 conf]# arp -an
? (134.95.19.54) at 00:02:B3:BE:8A:A6 [ether] PERM on eth2
? (134.95.19.28) at 00:03:BA:00:DA:E6 [ether] on eth2
? (134.95.19.58) at 00:02:B3:BE:8A:A6 [ether] PERM on eth2
? (134.95.19.30) at 08:00:20:A1:4C:FE [ether] on eth2
? (134.95.19.31) at 00:04:AC:7C:D8:08 [ether] on eth2
? (134.95.19.24) at 00:00:BE:A6:50:21 [ether] on eth2
? (134.95.19.25) at 08:00:20:72:92:B7 [ether] on eth2
? (134.95.19.27) at 08:00:20:9A:9E:C4 [ether] on eth2
? (134.95.19.7) at 00:03:BA:07:40:73 [ether] on eth2
? (134.95.19.104) at 00:03:47:73:0E:94 [ether] on eth2
? (192.168.20.3) at 00:B0:D0:D1:AB:E6 [ether] on eth0
? (134.95.19.105) at 00:02:B3:BE:8A:9E [ether] on eth2
? (192.168.20.5) at 00:06:5B:F0:5E:66 [ether] on eth0
? (134.95.19.3) at 08:00:20:72:92:C0 [ether] on eth2
? (192.168.20.7) at 00:06:5B:F0:F4:C4 [ether] on eth0
? (134.95.19.1) at 00:0B:60:AC:39:8A [ether] on eth2
? (192.168.20.6) at 00:06:5B:F0:5E:3E [ether] on eth0
? (134.95.19.14) at 00:03:BA:0C:9A:27 [ether] on eth2
? (134.95.19.43) at 00:03:47:9A:53:C6 [ether] on eth2
? (134.95.19.15) at 00:02:B3:BE:8A:A6 [ether] PERM on eth2
? (134.95.19.12) at 00:03:BA:0C:8E:79 [ether] on eth2
? (134.95.19.13) at 00:03:BA:07:40:74 [ether] on eth2
? (134.95.19.103) at 00:03:47:73:0E:92 [ether] on eth2
? (134.95.19.47) at 00:03:47:9A:53:7D [ether] on eth2
? (134.95.19.11) at 08:00:20:82:BA:70 [ether] on eth2
? (134.95.19.44) at 00:03:47:9A:53:34 [ether] on eth2
> ip neigh
[root@lvr7 root]# ip neigh
134.95.19.54 dev eth2 lladdr 00:02:b3:be:8a:9e nud permanent
134.95.19.30 dev eth2 lladdr 08:00:20:a1:4c:fe nud reachable
134.95.19.27 dev eth2 lladdr 08:00:20:9a:9e:c4 nud reachable
134.95.19.106 dev eth2 lladdr 00:02:b3:be:8a:a6 nud reachable
192.168.19.254 dev eth2 lladdr 00:02:b3:be:8a:9e nud permanent
192.168.19.5 dev eth2 lladdr 00:03:47:73:0e:92 nud reachable
134.95.19.1 dev eth2 lladdr 00:0b:60:ac:39:8a nud reachable
192.168.19.6 dev eth2 lladdr 00:03:47:73:0e:94 nud reachable
134.95.19.42 dev eth2 lladdr 00:03:47:9a:53:7d nud stale
192.168.20.8 dev eth0 lladdr 00:06:5b:f0:f4:c9 nud reachable
134.95.19.15 dev eth2 lladdr 00:02:b3:be:8a:9e nud permanent
134.95.19.44 dev eth2 lladdr 00:03:47:9a:53:34 nud stale
[root@lvr8 conf]# ip neigh
134.95.19.54 dev eth2 lladdr 00:02:b3:be:8a:a6 nud permanent
134.95.19.28 dev eth2 lladdr 00:03:ba:00:da:e6 nud reachable
134.95.19.58 dev eth2 lladdr 00:02:b3:be:8a:a6 nud permanent
134.95.19.30 dev eth2 lladdr 08:00:20:a1:4c:fe nud delay
134.95.19.24 dev eth2 lladdr 00:00:be:a6:50:21 nud reachable
134.95.19.25 dev eth2 lladdr 08:00:20:72:92:b7 nud reachable
134.95.19.27 dev eth2 lladdr 08:00:20:9a:9e:c4 nud delay
134.95.19.7 dev eth2 lladdr 00:03:ba:07:40:73 nud stale
192.168.20.3 dev eth0 lladdr 00:b0:d0:d1:ab:e6 nud reachable
134.95.19.105 dev eth2 lladdr 00:02:b3:be:8a:9e nud reachable
192.168.20.5 dev eth0 lladdr 00:06:5b:f0:5e:66 nud stale
134.95.19.3 dev eth2 lladdr 08:00:20:72:92:c0 nud reachable
192.168.20.7 dev eth0 lladdr 00:06:5b:f0:f4:c4 nud delay
134.95.19.1 dev eth2 lladdr 00:0b:60:ac:39:8a nud reachable
192.168.20.6 dev eth0 lladdr 00:06:5b:f0:5e:3e nud stale
134.95.19.14 dev eth2 lladdr 00:03:ba:0c:9a:27 nud stale
134.95.19.43 dev eth2 lladdr 00:03:47:9a:53:c6 nud stale
134.95.19.15 dev eth2 lladdr 00:02:b3:be:8a:a6 nud permanent
134.95.19.13 dev eth2 lladdr 00:03:ba:07:40:74 nud stale
134.95.19.11 dev eth2 lladdr 08:00:20:82:ba:70 nud reachable
Ok, that's the lot. I hope you can make anything of it; I sure don't
:-). (At least not from 'ip neigh')
Thanks again for your help!
Dipl. Chem. Dr. Stephan Wonczak
Institut fuer Angewandte Informatik (ZAIK)
Regionales Rechenzentrum der Universitaet zu Koeln (RRZK)
Universitaet zu Koeln, Robert-Koch-Strasse 10, 50931 Koeln
Tel: ++49/(0)221/478-5577, Fax: ++49/(0)221/478-5590
|
