From: Stephen Hemminger <shemminger@linux-foundation.org>
To: Roman Lisagor <RLisagor@wurldtech.com>
Cc: bridge@linux-foundation.org
Subject: Re: [Bridge] Trouble with bridged interfaces
Date: Fri, 15 Jun 2007 09:21:00 -0700 [thread overview]
Message-ID: <20070615092100.5df0c045@localhost> (raw)
In-Reply-To: <63CB92BFF23FC54A8CF2F4A67654B24601F5D163@i-worx-srv-02.i-worx.ca>
On Wed, 13 Jun 2007 18:28:07 -0700
"Roman Lisagor" <RLisagor@wurldtech.com> wrote:
> Hi,
>
> We need to bridge several interfaces together, but still retain the
> ability to communicate through the individual interfaces. So for
> example, we have eth0 and eth1 bridged and we bind IP addresses to both
> of them, in order to inject packets into communication between two
> devices connected to our interfaces.
>
Addresses in Linux aren't assigned to interfaces.
Look up the regular questions that come up about Linux responding
to ARP on the wrong interface.
> It seems that several problems arise intermittently:
>
> 1. When sending ping requests, replies sometimes come in on eth0/1, but
> sometimes on br0. We can work around this, but it would be great to get
> some idea of why and when this happens (and possibly whether we can
> prevent it from occurring);
>
> 2. Occasionally, ARP requests sent by external devices for the IPs of
> eth0/1 are ignored.
>
> We are running Fedora Core 6 (2.6.13-15-smp).
> Any ideas?
>
> Thanks in advance for your help.
>
> Roman
Go up your requirements, why do you need to do things this way?
There may be better alternatives
next prev parent reply other threads:[~2007-06-15 16:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 1:28 [Bridge] Trouble with bridged interfaces Roman Lisagor
2007-06-15 16:21 ` Stephen Hemminger [this message]
2007-06-15 22:39 ` Brad Dameron
2007-06-15 23:24 ` Roman Lisagor
2007-06-16 0:20 ` Stephen Hemminger
-- strict thread matches above, loose matches on Subject: below --
2007-06-14 17:22 Roman Lisagor
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=20070615092100.5df0c045@localhost \
--to=shemminger@linux-foundation.org \
--cc=RLisagor@wurldtech.com \
--cc=bridge@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox