From: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
To: Patrick McHardy <kaber@trash.net>
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, 07 Feb 2013 12:58:01 +0100 [thread overview]
Message-ID: <511396C9.2080106@profihost.ag> (raw)
In-Reply-To: <20130207112227.GE13989@macbook.localnet>
[-- Attachment #1: Type: text/plain, Size: 2195 bytes --]
Hi Patrick,
thanks for your fast response.
> So please describe the entire GVRP message exchange that's going
> on.
I've attached two small pcap files.
has_bridge.pcap: is where eth1 has a bridge and the dynamic vlan
disappears after a few seconds.
no_bridge.pcap: no bridge is assigned to eth1 - the dynamic vlan stays
as long as i remove it
> 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.
That's working fine in vanilla kernel 3.7.6 but it does not with RHEL 6.
Also i looks more complicated as i need another bridge on top of the
vlan to assign the needed tap devices. I looked at ovirt for the network
setup:
http://www.ovirt.org/Vdsm_Network
and they also add the vlan directly on top of the nic and then the
bridge on top of the VLANs.
Greets,
Stefan
Am 07.02.2013 12:22, schrieb Patrick McHardy:
> 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.
>
[-- Attachment #2: no_bridge.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 2838 bytes --]
[-- Attachment #3: has_bridge.pcap --]
[-- Type: application/vnd.tcpdump.pcap, Size: 2730 bytes --]
next prev parent reply other threads:[~2013-02-07 11:58 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
2013-02-07 11:58 ` Stefan Priebe - Profihost AG [this message]
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=511396C9.2080106@profihost.ag \
--to=s.priebe@profihost.ag \
--cc=aderumier@odiso.com \
--cc=davem@davemloft.net \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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