From: Vlad Yasevich <vyasevic@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: David Miller <davem@davemloft.net>,
Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: VLAN filtering/VLAN aware bridge problems
Date: Tue, 10 Sep 2013 10:11:19 -0400 [thread overview]
Message-ID: <522F2887.1080300@redhat.com> (raw)
In-Reply-To: <2036307B-46CC-40F6-ACE0-93A08BDEE0B9@profihost.ag>
On 08/30/2013 11:01 AM, Stefan Priebe - Profihost AG wrote:
> Yes
>
Can you apply this patch and see if this fixes your problem.
http://patchwork.ozlabs.org/patch/273841/
In my attempts to reproduce your problem I didn't configuring filtering
on the upper bridge, but that is what could have been causing
your problem. I'll attempt it and let you know.
-vlad
> Stefan
>
> This mail was sent with my iPhone.
>
> Am 30.08.2013 um 16:13 schrieb Vlad Yasevich <vyasevic@redhat.com>:
>
>> On 08/30/2013 03:24 AM, Stefan Priebe - Profihost AG wrote:
>>> Am 29.08.2013 22:45, schrieb Vlad Yasevich:
>>>> On 08/29/2013 08:50 AM, Stefan Priebe - Profihost AG wrote:
>>>
>>>>> The packets never reach the TAP device.
>>>>>
>>>>> Here is an output of ip a l (vlan 3021):
>>>>
>>>> Can you provide output of brctl show?
>>>
>>> Sure:
>>> # brctl show
>>> bridge name bridge id STP enabled interfaces
>>> vmbr0 8000.00259084dea8 no bond0
>>> tap320i0
>>> vmbr1 8000.00259084deaa no bond1
>>> vmbr1v3021 8000.00259084deaa no tap320i1
>>> vmbr1.3021
>>
>> so let me see if I can understand this configuration.
>>
>> vmbr1v3021 (bridge)
>> / \
>> tap320i1 vmbr1.3021 (vlan)
>> \
>> vmbr1 (bridge)
>> \
>> bond1
>> \
>> eth X
>>
>>
>> Is that right? Is this the setup that has the problem you are
>> describing?
>>
>> Thanks
>> -vlad
>>
>>>> On the off chance that you are actually trying to configure vlan
>>>> filtering, can you give this patch a try (net-2.6 tree):
>>>>
>>>> Author: Toshiaki Makita <makita.toshiaki@lab.ntt.co.jp>
>>>> Date: Tue Aug 20 17:10:18 2013 +0900
>>>>
>>>> bridge: Use the correct bit length for bitmap functions in the VLAN
>>>> code
>>>>
>>>> I don't think it made it to stable yet.
>>>
>>> I addd that patch and now the vlan stuff works at least on the host
>>> node. But my tap devices still don't work.
>>>
>>> I also tried to attach the tap device on top of a vlan attached to bond1
>>> but then gvrp does not work anymore. The kernel announces gvrp once and
>>> then does not answer the query packets from the switch.
>>>
>>> Stefan
>>
next prev parent reply other threads:[~2013-09-10 14:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 12:50 VLAN filtering/VLAN aware bridge problems Stefan Priebe - Profihost AG
2013-08-29 20:45 ` Vlad Yasevich
2013-08-30 7:24 ` Stefan Priebe - Profihost AG
2013-08-30 14:13 ` Vlad Yasevich
2013-08-30 15:01 ` Stefan Priebe - Profihost AG
2013-08-30 15:01 ` Stefan Priebe - Profihost AG
2013-09-10 14:11 ` Vlad Yasevich [this message]
2013-11-12 21:31 ` Stefan Priebe
2013-11-12 23:25 ` Vlad Yasevich
2013-11-13 7:28 ` Stefan Priebe - Profihost AG
2013-11-13 14:49 ` Vlad Yasevich
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=522F2887.1080300@redhat.com \
--to=vyasevic@redhat.com \
--cc=davem@davemloft.net \
--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;
as well as URLs for NNTP newsgroup(s).