Developing the explanation a little further, I thought the proxy-arp code was supposed to be intelligent to the point of *not* answering arp queries for 192.168.120.x and for 192.168.220.x coming from eth0 IF eth0=192.168.220.1 and eth0:1=192.168.120.1. But I think it is doing it. Is there a way to delay the reply, perhaps, or even prevent it from doing it at all like it should be happening? Thanks, Nuno > -----Original Message----- > From: linux-net-owner@vger.kernel.org > [mailto:linux-net-owner@vger.kernel.org] On Behalf Of Nuno > Filipe R. Ferreira > Sent: segunda-feira, 11 de Fevereiro de 2002 13:04 > To: linux-net@vger.kernel.org > Subject: proxy arp > > > Hi, > > Is anyone aware of problems with auto proxy arp feature in Linux, > regarding ip conflicts? > > This is a machine with several eth's, on two of them - eth0 (internal > LAN) and eth1 (router with crossover cable) - I have proxy > arp enabled. > eth0 is further divided into eth0 (192.168.220.0/24) and eth0:1 > (192.168.120.0/24). What seems to be happening is that all the new > windows (2K Pro|XP) machines booting with addresses 192.168.120.x are > getting ip conflicts. > > The same problem seems to be keeping me from using DHCP. > > If I echo 0 > /proc/sys/net/ipv4/conf/eth0/proxy_arp, then boot the > machines or disable/enable the interfaces and then echo 1 > > /proc/sys/net/ipv4/conf/eth0/proxy_arp it will work, but this > *can't* be > the solution. > > RH 7.2 with kernel 2.4.17. > > TIA, > nuno > > - > : 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 > - : 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
