From: Patrick McHardy <kaber@trash.net>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: Linux Netdev List <netdev@vger.kernel.org>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>,
Alexandre DERUMIER <aderumier@odiso.com>
Subject: Re: Problem with GVRP on eth while having a bridge
Date: Thu, 7 Feb 2013 12:22:27 +0100 [thread overview]
Message-ID: <20130207112227.GE13989@macbook.localnet> (raw)
In-Reply-To: <51138866.8000802@profihost.ag>
On Thu, Feb 07, 2013 at 11:56:38AM +0100, Stefan Priebe - Profihost AG wrote:
> Hello list,
>
> this was tested using vanilla 3.7.6 kernel.
>
> When i add a vlan to an ethernet device supporting gvrp everything is
> fine until this ethernet device also had a bridge.
>
> This works fine as long as eth1 is not attached to a bridge.
>
> # ip link add link eth1 name eth1.99 type vlan id 99 gvrp on
> # ip link set eth1.99 up
>
> The dynamic VLAN stays up at the switch - no problems.
>
> If eth1 has a bridge the dynamic vlan is created at the switch so the
> initial packet was send but it disappears after a few seconds.
>
> Wireshark shows that the kernel has stopped sending GVRP packets. After
> adding a bridge to eth1.
Well, there's no reason why it should continue sending packets after
the switch has been updated unless it receives a message indicating
that the switch is about to remove it from it's tables again. So
please describe the entire GVRP message exchange that's going on.
Also you probably want to add the VLAN device on top of the bridge
device, otherwise it will get passed to the bridge after untagging,
which might not work, depending on the MAC addresses used.
next prev parent reply other threads:[~2013-02-07 11:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-07 10:56 Problem with GVRP on eth while having a bridge Stefan Priebe - Profihost AG
2013-02-07 11:22 ` Patrick McHardy [this message]
2013-02-07 11:58 ` Stefan Priebe - Profihost AG
2013-02-07 13:02 ` Patrick McHardy
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=20130207112227.GE13989@macbook.localnet \
--to=kaber@trash.net \
--cc=aderumier@odiso.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=s.priebe@profihost.ag \
/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