netdev - Re: [Bugme-new] [Bug 35862] New: arp requests from wrong src IP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20110525.215222.22117057747103565.davem@davemloft.net>
Date:	Wed, 25 May 2011 21:52:22 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	akpm@...ux-foundation.org
Cc:	netdev@...r.kernel.org, bugzilla-daemon@...zilla.kernel.org,
	bugme-daemon@...zilla.kernel.org, matare@....rwth-aachen.de
Subject: Re: [Bugme-new] [Bug 35862] New: arp requests from wrong src IP

From: Andrew Morton <akpm@...ux-foundation.org>
Date: Wed, 25 May 2011 16:31:37 -0700

>> I switched a host's ip address from 137.226.164.13 to 137.226.164.2. The .13 IP
>> now belongs to the host that had .2 before (I swapped them). Now both hosts
>> still arp from their old IPs although ifconfig as well as ip clearly tell
>> otherwise. Examining the host which now has 137.226.164.13:
>> 
>> # ip addr show dev eth0
>> 4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
>>     link/ether 00:e0:81:41:1f:e4 brd ff:ff:ff:ff:ff:ff
>>     inet 137.226.164.2/24 brd 137.226.164.255 scope global eth0
>>     inet 192.168.23.2/24 brd 137.226.164.255 scope global eth0:0

If you keep the old IP address around it remains as the "primary"
IP address.

You have to explicitly remove the original IP address from the
interface first, then add the new one, in order for the new
one to become the "primary"

Not a bug, please close this.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html