All of lore.kernel.org
 help / color / mirror / Atom feed
From: Veaceslav Falico <vfalico@redhat.com>
To: Stefan Priebe - Profihost AG <s.priebe@profihost.ag>
Cc: vyasevic@redhat.com, Vlad Yasevich <vyasevich@gmail.com>,
	Linux Netdev List <netdev@vger.kernel.org>
Subject: Re: how to mix bridges and bonding inc. vlans correctly on Kernel > 3.10
Date: Thu, 14 Nov 2013 13:29:28 +0100	[thread overview]
Message-ID: <20131114122928.GV19702@redhat.com> (raw)
In-Reply-To: <52848010.8030103@profihost.ag>

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@vger.kernel.org
>More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-11-14 12:31 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-13 13:58 how to mix bridges and bonding inc. vlans correctly on Kernel > 3.10 Stefan Priebe - Profihost AG
2013-11-13 14:12 ` Veaceslav Falico
2013-11-13 14:20   ` Stefan Priebe - Profihost AG
2013-11-13 14:34     ` Veaceslav Falico
2013-11-13 14:43       ` Stefan Priebe - Profihost AG
2013-11-13 15:05     ` Vlad Yasevich
2013-11-13 15:17       ` Stefan Priebe - Profihost AG
2013-11-13 16:21         ` Veaceslav Falico
2013-11-13 16:43           ` Stefan Priebe - Profihost AG
2013-11-13 17:21           ` Vlad Yasevich
2013-11-13 20:09             ` Stefan Priebe
2013-11-14  3:09               ` Vlad Yasevich
2013-11-14  7:47                 ` Stefan Priebe - Profihost AG
2013-11-14 12:29                   ` Veaceslav Falico [this message]
2013-11-14 21:13                     ` Vlad Yasevich
2013-11-16 21:02                       ` Stefan Priebe
2013-11-17  3:41                         ` Vladislav Yasevich
2013-11-18  7:37                           ` Stefan Priebe - Profihost AG
2013-11-14 11:54                 ` Veaceslav Falico
2013-11-14 14:27                   ` Vlad Yasevich
2013-11-14 14:29                     ` Stefan Priebe - Profihost AG
2013-11-14 14:41                       ` Vlad Yasevich
2013-11-16 21:00                         ` Stefan Priebe
2013-11-13 16:44         ` Vlad Yasevich
2013-11-13 17:22           ` Stefan Priebe - Profihost AG
2013-11-13 17:37             ` Vlad Yasevich
2013-11-13 17:46               ` Stefan Priebe - Profihost AG
2013-11-13 17: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=20131114122928.GV19702@redhat.com \
    --to=vfalico@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=s.priebe@profihost.ag \
    --cc=vyasevic@redhat.com \
    --cc=vyasevich@gmail.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.