netdev
[Top] [All Lists]

Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases

To: netdev@xxxxxxxxxxx
Subject: Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases
From: Andrew Morton <akpm@xxxxxxxx>
Date: Thu, 28 Oct 2004 23:46:49 -0700
Cc: mbm@xxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx

Begin forwarded message:

Date: Thu, 28 Oct 2004 23:45:02 -0700
From: bugme-daemon@xxxxxxxx
To: bugme-new@xxxxxxxxxxxxxx
Subject: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases


http://bugme.osdl.org/show_bug.cgi?id=3657

           Summary: downed interfaces acting as aliases
    Kernel Version: 2.6.8.1
            Status: NEW
          Severity: normal
             Owner: shemminger@xxxxxxxx
         Submitter: mbm@xxxxxxx


An interface will still reply while down, acting as an ip alias if any other
adapters have a compatible subnet.

Scenerio:

Using a laptop on a wired network, 192.168.1.0/24 subnet, eth0 set to
192.168.1.2. Moved to a different network on wireless, also a 192.168.1.0/24. 

The ethernet is still configured for 192.168.1.2 but the interface is down
(ifconfig eth0 down); wireless clients on the second network are now having
issues, 192.168.1.2 requests are going to the laptop.

To confirm the issue, eth0 is changed to 192.168.1.254 and brought down again
(an ip not in use on the wireless network). All wireless clients are magically
able to ping 192.168.1.254.


Steps to reproduce:

ifconfig eth0 10.1.2.3 (or any random nonroutable ip)
ifconfig eth0 down
ping 10.1.2.3

.. wtf, how did it get a reply from a down'd interface?

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.

<Prev in Thread] Current Thread [Next in Thread>