From: "Prof. Brand " <brand@jupiter.cs.uni-dortmund.de>
To: timothy.covell@ashavan.org
Cc: "Pei Zheng" <zhengpei@msu.edu>, linux-kernel@vger.kernel.org
Subject: Re: strange kernel message when hacking the NIC driver
Date: Sat, 12 Jan 2002 22:37:11 +0100 [thread overview]
Message-ID: <200201122137.g0CLbCR26740@jupiter.cs.uni-dortmund.de> (raw)
In-Reply-To: Message from Timothy Covell <timothy.covell@ashavan.org> of "Fri, 11 Jan 2002 05:55:20 CST." <200201111159.g0BBxCSr001144@svr3.applink.net>
Timothy Covell <timothy.covell@ashavan.org> said:
> On Thursday 10 January 2002 23:20, Timothy Covell wrote:
> Let me clarify what I said earlier. You cannot have
> identical MAC addresses on two different NICs.
You sure can. Look at your nearest Sun machine with two NICs for an
example.
> Indeed,
> it is impossible w/o trying to fool the kernel into
> redefining the NICs hardware based MAC address.
It is not "fooling", you can set the MAC address on some cards by software.
Kernel has nothing to do with it.
> As concerns TCP/IP, you can define two NICs to have the
> same IP address, but you will only end up confusing
> your switch/HUB router which assumes a 1 to 1 mapping
> of MACs to IPs. The whole point of ICMP is to
> discover this mapping via ARP requests.
TCP/IP is a 4(5) level protocol stack:
0 Hardware [Cribbed from ISO]
1 Device driver
2 IP [Includes ICMP]
3 TCP and UDP
4 Applications
A switch/hub works on Ethernet frames, i.e., at the hardware level. It has
absolutely no idea of mappings of MACs to IPs.
ICMP is part of the IP layer, the whole of the mapping of IPs to MACs is
(conceptually at least) part of the device driver layer. This includes ARP,
DHCP et al. ICMP has nothing to do with ARP.
--
Horst von Brand http://counter.li.org # 22616
next prev parent reply other threads:[~2002-01-12 21:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-11 4:19 Pei Zheng
2002-01-11 5:20 ` Timothy Covell
2002-01-11 11:55 ` Timothy Covell
2002-01-11 13:11 ` Alan Cox
2002-01-11 19:02 ` Timothy Covell
2002-01-11 19:24 ` Paul Walmsley
2002-01-11 22:51 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand [this message]
2002-01-12 21:58 ` Timothy Covell
2002-01-11 12:07 ` David S. Miller
2002-01-11 12:20 ` Timothy Covell
2002-01-12 21:37 ` Prof. Brand
2002-01-12 21:44 ` Timothy Covell
2002-01-11 12:28 ` David S. Miller
2002-01-11 19:33 ` Pei Zheng
2002-01-14 6:32 Zwane Mwaikambo
2002-01-14 7:41 ` Bernd Eckenfels
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=200201122137.g0CLbCR26740@jupiter.cs.uni-dortmund.de \
--to=brand@jupiter.cs.uni-dortmund.de \
--cc=linux-kernel@vger.kernel.org \
--cc=timothy.covell@ashavan.org \
--cc=zhengpei@msu.edu \
/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
all inboxes | Powered by JetHome®