From: Vlad Yasevich <vyasevic@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"Oleg A. Arkhangelsky" <sysoleg@yandex.ru>
Subject: Re: [Bridge] [PATCH net-next 0/4] Allow bridge to function in non-promisc mode
Date: Wed, 13 Mar 2013 11:45:40 -0400 [thread overview]
Message-ID: <51409F24.3070305@redhat.com> (raw)
In-Reply-To: <20130313083932.6483876f@nehalam.linuxnetplumber.net>
On 03/13/2013 11:39 AM, Stephen Hemminger wrote:
> On Wed, 13 Mar 2013 08:12:29 -0400
> Vlad Yasevich <vyasevic@redhat.com> wrote:
>
>> On 03/13/2013 02:22 AM, "Oleg A. Arkhangelsky" wrote:
>>>
>>>
>>> 13.03.2013, 05:45, "Vlad Yasevich" <vyasevic@redhat.com>:
>>>
>>>> The series adds an ability for the bridge to function in non-promiscuous mode.
>>>
>>> What is the practical applications for such setup? In other words,
>>> in which cases I would want to put bridge into non-promiscuous
>>> mode and specify some uplink ports?
>>>
>>
>> On of the applications would be when bridge is an edge device servicing
>> a VM deployment. Each of the VMs knows the mac address that the guest
>> has and may program that mac onto the uplinks.
>
> Why wouldn't that environment just use macvlan?
> Is it because changing libvirt is harder than changing the kernel?
>
No, because macvlan has a drawback that it doesn't easily let guests
talk to the host. Bridge is still most commonly used for just that reason.
-vlad
WARNING: multiple messages have this Message-ID (diff)
From: Vlad Yasevich <vyasevic@redhat.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>,
"Oleg A. Arkhangelsky" <sysoleg@yandex.ru>
Subject: Re: [PATCH net-next 0/4] Allow bridge to function in non-promisc mode
Date: Wed, 13 Mar 2013 11:45:40 -0400 [thread overview]
Message-ID: <51409F24.3070305@redhat.com> (raw)
In-Reply-To: <20130313083932.6483876f@nehalam.linuxnetplumber.net>
On 03/13/2013 11:39 AM, Stephen Hemminger wrote:
> On Wed, 13 Mar 2013 08:12:29 -0400
> Vlad Yasevich <vyasevic@redhat.com> wrote:
>
>> On 03/13/2013 02:22 AM, "Oleg A. Arkhangelsky" wrote:
>>>
>>>
>>> 13.03.2013, 05:45, "Vlad Yasevich" <vyasevic@redhat.com>:
>>>
>>>> The series adds an ability for the bridge to function in non-promiscuous mode.
>>>
>>> What is the practical applications for such setup? In other words,
>>> in which cases I would want to put bridge into non-promiscuous
>>> mode and specify some uplink ports?
>>>
>>
>> On of the applications would be when bridge is an edge device servicing
>> a VM deployment. Each of the VMs knows the mac address that the guest
>> has and may program that mac onto the uplinks.
>
> Why wouldn't that environment just use macvlan?
> Is it because changing libvirt is harder than changing the kernel?
>
No, because macvlan has a drawback that it doesn't easily let guests
talk to the host. Bridge is still most commonly used for just that reason.
-vlad
next prev parent reply other threads:[~2013-03-13 15:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-13 1:45 [Bridge] [PATCH net-next 0/4] Allow bridge to function in non-promisc mode Vlad Yasevich
2013-03-13 1:45 ` Vlad Yasevich
2013-03-13 1:45 ` [Bridge] [PATCH net-next 1/4] bridge: Add sysfs interface to control promisc mode Vlad Yasevich
2013-03-13 1:45 ` Vlad Yasevich
2013-03-13 15:38 ` [Bridge] " Stephen Hemminger
2013-03-13 15:38 ` Stephen Hemminger
2013-03-13 15:44 ` [Bridge] " Vlad Yasevich
2013-03-13 15:44 ` Vlad Yasevich
2013-03-13 1:45 ` [Bridge] [PATCH net-next 2/4] bridge: Allow an ability to designate an uplink port Vlad Yasevich
2013-03-13 1:45 ` Vlad Yasevich
2013-03-13 20:33 ` [Bridge] " Michael S. Tsirkin
2013-03-13 20:33 ` Michael S. Tsirkin
2013-03-13 22:54 ` [Bridge] " Stephen Hemminger
2013-03-13 22:54 ` Stephen Hemminger
2013-03-13 23:43 ` [Bridge] " Vlad Yasevich
2013-03-13 23:43 ` Vlad Yasevich
2013-03-14 14:53 ` [Bridge] " Dan Williams
2013-03-14 14:53 ` Dan Williams
2013-03-13 1:45 ` [Bridge] [PATCH net-next 3/4] bridge: Implement IFF_UNICAST_FLT Vlad Yasevich
2013-03-13 1:45 ` Vlad Yasevich
2013-03-13 1:45 ` [Bridge] [PATCH net-next 4/4] bridge: sync device list when a new uplink is designated Vlad Yasevich
2013-03-13 1:45 ` Vlad Yasevich
2013-03-13 6:22 ` [Bridge] [PATCH net-next 0/4] Allow bridge to function in non-promisc mode "Oleg A. Arkhangelsky"
2013-03-13 6:22 ` "Oleg A. Arkhangelsky"
2013-03-13 12:12 ` [Bridge] " Vlad Yasevich
2013-03-13 12:12 ` Vlad Yasevich
2013-03-13 15:39 ` [Bridge] " Stephen Hemminger
2013-03-13 15:39 ` Stephen Hemminger
2013-03-13 15:45 ` Vlad Yasevich [this message]
2013-03-13 15:45 ` Vlad Yasevich
2013-03-13 16:09 ` [Bridge] " Stephen Hemminger
2013-03-13 16:09 ` Stephen Hemminger
2013-03-13 17:04 ` [Bridge] " Vlad Yasevich
2013-03-13 17:04 ` Vlad Yasevich
2013-03-13 18:56 ` [Bridge] " Joel Wirāmu Pauling
2013-03-13 20:08 ` Michael S. Tsirkin
2013-03-13 20:08 ` Michael S. Tsirkin
2013-03-13 20:31 ` [Bridge] " Michael S. Tsirkin
2013-03-13 20:31 ` Michael S. Tsirkin
2013-03-14 15:10 ` [Bridge] " Vlad Yasevich
2013-03-14 15:10 ` Vlad Yasevich
2013-03-14 17:46 ` [Bridge] " Michael S. Tsirkin
2013-03-14 17:46 ` Michael S. Tsirkin
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=51409F24.3070305@redhat.com \
--to=vyasevic@redhat.com \
--cc=bridge@lists.linux-foundation.org \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
--cc=sysoleg@yandex.ru \
/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.