From: Thomas Mueller <thomas@chaschperli.ch>
To: bridge@osdl.org
Subject: [Bridge] bridge changes id on addif - is that normal?
Date: Sat, 22 Nov 2008 13:43:37 +0000 (UTC) [thread overview]
Message-ID: <gg92a9$5ot$1@ger.gmane.org> (raw)
hi
i've setup the following on debian etch with bridge-utils 1.4
(backported) and kernel 2.6.26 from backports.org:
vlan10 with raw device eth0
vlan20 with raw device eth0
br10 with initial port vlan10
br20 with initial port vlan20
i've set hw addr to DE:AD:BE:EF:34:10 for br10 and DE:AD:BE:EF:34:20 for
br20
the bridges are used to connect virtual machine nic's.
"brctl show" before any other port is attached:
bridge name bridge id STP enabled interfaces
br10 8000.deadbeef3410 no vlan10
br20 8000.deadbeef3420 no vlan20
then after "brctl addif br10 vnet1" and "brctl addif br10 vnet2" brctl
show says:
bridge name bridge id STP enabled interfaces
br10 8000.00ff351a360c no vnet1
vlan10
br20 8000.00ff8fe8ee1d no vnet2
vlan20
why the bridge id changed? on delif the bridge id changes back to the
original one.
On "brctl addbr" the following kernel message is printed:
[426666.180613] br10: Dropping NETIF_F_UFO since no NETIF_F_HW_CSUM
feature.
if i don't set the mac addr to the bridges they get both the hw addr from
eth0. the bridge id doesn't change on addif but there are many kernel
messages like the one below:
[405275.752398] vnet1: received packet with own address as source address
Any hints appreciated.
- Thomas
next reply other threads:[~2008-11-22 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-22 13:43 Thomas Mueller [this message]
2008-11-22 15:47 ` [Bridge] bridge changes id on addif - is that normal? Thomas Mueller
2008-11-23 6:40 ` Stephen Hemminger
2008-11-23 12:26 ` Thomas Mueller
2008-11-23 13:29 ` Dietmar Maurer
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='gg92a9$5ot$1@ger.gmane.org' \
--to=thomas@chaschperli.ch \
--cc=bridge@osdl.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.