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 17:20:38 -0700 [thread overview]
Message-ID: <20070615172038.37973c22@localhost> (raw)
In-Reply-To: <63CB92BFF23FC54A8CF2F4A67654B24601F863D7@i-worx-srv-02.i-worx.ca>
On Fri, 15 Jun 2007 16:24:56 -0700
"Roman Lisagor" <RLisagor@wurldtech.com> wrote:
> Hi Stephen,
>
> We are doing this for a network testing product. Our box sits between
> two devices (e.g. one connected to eth0 and one to eth1) which
> communicate with each other, so we bridge the two interfaces to maintain
> communication between the two sides. One of the devices (connected to
> eth0) is under test so we need to send and receive traffic to and from
> that device and want to be sure that none of the _test_ traffic is also
> going to eth1. Raw sockets are used to create the traffic on eth0.
>
> In most cases this works well, but in some cases (which are very
> difficult to reproduce or determine the pattern for) we see incoming
> packets on the bridge instead of the interface.
>
> Also, what do you mean when you say that addresses are not assigned to
> interfaces? (Isn't that the result of running "ifconfig ethX
> ip.ip.ip.ip"?)
>
> Thanks again,
> Roman.
>
A per previous suggestion, use ebtables. It is the best way
to get selective traffic control or any other hacks.
next prev parent reply other threads:[~2007-06-16 0:20 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
2007-06-15 22:39 ` Brad Dameron
2007-06-15 23:24 ` Roman Lisagor
2007-06-16 0:20 ` Stephen Hemminger [this message]
-- 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=20070615172038.37973c22@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