From: Andrew Morton <akpm@osdl.org>
To: netdev@oss.sgi.com
Cc: mbm@alt.org
Subject: Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases
Date: Thu, 28 Oct 2004 23:46:49 -0700 [thread overview]
Message-ID: <20041028234649.2d4ed3b8.akpm@osdl.org> (raw)
Begin forwarded message:
Date: Thu, 28 Oct 2004 23:45:02 -0700
From: bugme-daemon@osdl.org
To: bugme-new@lists.osdl.org
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@osdl.org
Submitter: mbm@alt.org
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.
next reply other threads:[~2004-10-29 6:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-29 6:46 Andrew Morton [this message]
2004-10-29 6:45 ` Fw: [Bugme-new] [Bug 3657] New: downed interfaces acting as aliases David S. Miller
2004-10-29 7:10 ` Ben Greear
2004-10-29 7:06 ` David S. Miller
2004-10-29 7:28 ` Ben Greear
2004-10-29 7:39 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20041028234649.2d4ed3b8.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=mbm@alt.org \
--cc=netdev@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).