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]

Date:	Thu, 14 Nov 2013 13:29:28 +0100
From:	Veaceslav Falico <vfalico@...hat.com>
To:	Stefan Priebe - Profihost AG <s.priebe@...fihost.ag>
Cc:	vyasevic@...hat.com, Vlad Yasevich <vyasevich@...il.com>,
	Linux Netdev List <netdev@...r.kernel.org>
Subject: Re: how to mix bridges and bonding inc. vlans correctly on Kernel >
 3.10

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.

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