netdev - Re: how to mix bridges and bonding inc. vlans correctly on Kernel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CAGCdqXEQwHy_q+qWQf9oYTkr0v_HXLY-nudjW=4ghYpB+o3H1w@mail.gmail.com>
Date:	Sat, 16 Nov 2013 22:41:52 -0500
From:	Vladislav Yasevich <vyasevich@...il.com>
To:	Stefan Priebe <s.priebe@...fihost.ag>
Cc:	Veaceslav Falico <vfalico@...hat.com>,
	Vlad Yasevich <vyasevic@...hat.com>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: how to mix bridges and bonding inc. vlans correctly on Kernel > 3.10

On Sat, Nov 16, 2013 at 4:02 PM, Stefan Priebe <s.priebe@...fihost.ag> wrote:
> Am 14.11.2013 22:13, schrieb Vlad Yasevich:
>
>> On 11/14/2013 07:29 AM, Veaceslav Falico wrote:
>>>
>>> On Thu, Nov 14, 2013 at 08:47:28AM +0100, Stefan Priebe - Profihost AG
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>>> eth2
>>>>>      \
>>>>>       -- bond1 -- vmbr1
>>>>>      /     \
>>>>> eth3        ----- bond1.3000 --- vmbr1v3000
>>>>>                                      \ ---- tap114i1
>>>>
>>>>
>>>> thos one works fine now.
>>>>
>>>>
>>>>> eth2
>>>>>      \
>>>>>       -- bond1 -- vmbr1
>>>>>      /              \
>>>>> eth3                 \ vmbr1.3000
>>>>>                            \ ---- tap114i1
>>>>
>>>>
>>>> this one does not. Another note to this one. It also never worked on
>>>> RHEL6 - it started working with about 2.6.39 and stopped with 3.9 or
>>>> 3.10. But it was the only one where gvrp on vlans had worked.
>>>
>>>
>>> bridge device in this config is neither master nor slave, if I read it
>>> correctly.
>>
>>
>> Bridge doesn't propagate rx_flags to lower-level devices.  It
>> automatically set all lower devices to promisc mode.
>>
>> So, in the second case above, eth2 and eth3 have to be in promisc, but
>> nothing else does.  I am not sure I understand Stefans notation though
>> wrt to how vmbr1.3000 and tap114i1 are configured.  Stefan,  can you
>> elaborate?
>
>
> Sorry . means vlan - so vmbr1.3000 is just a vlan on top of vmbr1. *brX is a
> bridge. Bond is a lacp bond ;-)
>

Ok.  I got that.  But where is tap attached?  You are showing it
attached to the vlan,
but you can't do that unless its a macvtap.   macvtaps on top of bridges is just
asking for trouble.

Thanks
-vlad

> Stefan
>
>
>>
>> Thanks
>> -vlad
>>>
>>>
>>> You might want to try my patch to see if it works (my previous email).
>>>
>>>>
>>>> Greets,
>>>> 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
>>
>>
>
--
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