From: James Courtier-Dutton <James@superbug.co.uk>
To: Lehner franz <hamtitampti@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: BUG: Network: Duplicate MAC adress response in multihomed system : All Kernels
Date: Wed, 25 Oct 2006 19:24:53 +0100 [thread overview]
Message-ID: <453FABF5.6080209@superbug.co.uk> (raw)
In-Reply-To: <aa4884ff0610241353m4bc1ebebh92191fbf8aef9178@mail.gmail.com>
Lehner franz wrote:
> Maybe it is a setting, i have searched everywhere, but this is really
> mysterious
>
> take a linux, configure this kind
>
> eth0: 192.168.10.200 / 255.255.255.0
> eth1: 192.168.10.201 / 255.255.255.0
>
> Both Interfaces are "real ethernet cards" and are connected to same switch
>
> if you take now a 3'rd machine, and do a
>
> arping -c 1 192.168.10.200
>> 60 bytes from 00:0c:29:bc:96:fe ( 192.168.10.200): index=0
>> time=645.876 usec
>> 60 bytes from 00:0c:29:bc:96:f4 ( 192.168.10.200): index=1 time=1.472
>> msec
>
> arping -c 1 192.168.10.201
>> 60 bytes from 00:0c:29:bc:96:fe (192.168.10.201 ): index=0
>> time=833.988 usec
>> 60 bytes from 00:0c:29:bc:96:f4 (192.168.10.201): index=1 time=1.211 msec
>
This behavior is correct. You should not set up a network in the way you
have. Look at "bonding" for a better way to set up a system with
multiple physical interfaces on the same subnetwork.
James
next prev parent reply other threads:[~2006-10-25 18:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-24 20:53 BUG: Network: Duplicate MAC adress response in multihomed system : All Kernels Lehner franz
2006-10-25 18:24 ` James Courtier-Dutton [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 21:14 Lehner Franz
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=453FABF5.6080209@superbug.co.uk \
--to=james@superbug.co.uk \
--cc=hamtitampti@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.