[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <522F2887.1080300@redhat.com>
Date: Tue, 10 Sep 2013 10:11:19 -0400
From: Vlad Yasevich <vyasevic@...hat.com>
To: Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
CC: David Miller <davem@...emloft.net>,
Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: VLAN filtering/VLAN aware bridge problems
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@...hat.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@....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
>>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists