mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Timothy Covell <timothy.covell@ashavan.org>
To: timothy.covell@ashavan.org, "Pei Zheng" <zhengpei@msu.edu>,
	<linux-kernel@vger.kernel.org>
Subject: Re: strange kernel message when hacking the NIC driver
Date: Fri, 11 Jan 2002 05:55:20 -0600	[thread overview]
Message-ID: <200201111159.g0BBxCSr001144@svr3.applink.net> (raw)
In-Reply-To: <LIECKFOKGFCHAPOBKPECEEGCCNAA.zhengpei@msu.edu> <200201110524.g0B5OeSr000566@svr3.applink.net>
In-Reply-To: <200201110524.g0B5OeSr000566@svr3.applink.net>

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.   Indeed,
it is impossible w/o trying to fool the kernel into
redefining the NICs hardware based MAC address. 

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.

If you want to increase your aggregate bandwidth, then
there are several methods.  One is to use the bonding 
driver to make the NICs look like one but it needs to 
be supported by the switch that you use or for point-to-point 
connections, the other box. Another way is to use something 
like OSPF or advanced iptable routing to effect multipathing.  
Finally, a crude way to increase your effective bandwidth is 
to run several instances of your server(s) on different IP 
addresses/NICS but they cannot all have default routes on 
Linux without resorting to OSPF and/or iptables.


-- 
timothy.covell@ashavan.org.

  reply	other threads:[~2002-01-11 11:59 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 [this message]
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 
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=200201111159.g0BBxCSr001144@svr3.applink.net \
    --to=timothy.covell@ashavan.org \
    --cc=linux-kernel@vger.kernel.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®