From: "Salvador Fandiño" <sfandino@yahoo.com>
To: bridge@lists.linux-foundation.org
Subject: [Bridge] bridge iface drops everything
Date: Sat, 10 Mar 2012 12:11:57 +0100 [thread overview]
Message-ID: <4F5B36FD.3030206@yahoo.com> (raw)
Hi,
I have a machine, where I am running LXC containers on demand. These
containers don't need to talk to the outside, just between then and to
the host, so I am attaching them to an isolated bridge (br0) that
doesn't have any physical interface attached.
My problem is that by default, the bridge MAC is changed when new
containers are added or old ones removed causing the network to freeze
until ARP tables timeout (this is a known "feature").
I have tried to fix the bridge MAC address:
ip link set br0 address 00:11:22:33:44:55
But that doesn't work unless the MAC used correspond to the virtual
interfaces of one of the containers or if I make br0 in promiscuous
mode. Otherwise, br0 seems to drop all the traffic arriving there.
If seems that packets are not going up to the TCP/IP stack through the
bridge interface (br0) but through any of the interfaces attached to the
bridge that happens to have the same MAC.
Is this the expected behavior?
BTW, I am running SLES11 SP1 and SP2.
reply other threads:[~2012-03-10 11:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4F5B36FD.3030206@yahoo.com \
--to=sfandino@yahoo.com \
--cc=bridge@lists.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 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.