From: Marek Kierdelewicz <marek@piasta.pl>
To: Lambert Laurent <lambert.laurent91@gmail.com>
Cc: bridge@lists.linux-foundation.org
Subject: Re: [Bridge] Tap and Bridge problem
Date: Sun, 7 Jul 2013 21:56:34 +0200 [thread overview]
Message-ID: <20130707215634.1c63ed9e@catus> (raw)
In-Reply-To: <CAGZVhE1nOXBO_QiDX58xR3mu_sd6v2p3tiZPe+hKsJ3mS+UWEQ@mail.gmail.com>
> Hi,
Hi,
>I'm currently trying to use bridge and tap for my work. In my setup I
>use two programs communicating though tap interface. I connect the two
>tap interface with a bridge.
>...
>Now comes the problem, currently only broadcast or multicast frames
>goes through the bridge. Every unicast frame get drop (or stuck)
>between the
>Did anyone this behavior in the past time ?
Yes. Try using veth pair interfaces:
ip link add name veth1 type veth peer name veth2
You'll get veth1 and veth2 pair that act as a "wormhole". Now add veth1
to the bridge and use veth2 with your program in the way you used tap.
If you need second pair just repeat procedure with different interface
names.
Best regards,
Marek Kierdelewicz
next prev parent reply other threads:[~2013-07-07 19:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-06 15:22 [Bridge] Tap and Bridge problem Lambert Laurent
2013-07-07 19:56 ` Marek Kierdelewicz [this message]
2013-07-08 8:12 ` Lambert Laurent
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=20130707215634.1c63ed9e@catus \
--to=marek@piasta.pl \
--cc=bridge@lists.linux-foundation.org \
--cc=lambert.laurent91@gmail.com \
/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