Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Vlad Yasevich <vyasevic@xxxxxxxxxx>
Subject: Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
From: Stephen Hemminger <stephen@xxxxxxxxxxxxxxxxxx>
Date: Thu, 2 May 2013 10:23:31 -0700
Cc: netdev@xxxxxxxxxxxxxxx, bridge@xxxxxxxxxxxxxxxxxxxxxxxxxx, mst@xxxxxxxxxx
Delivered-to: bridge@xxxxxxxxxxxxxxxxxxxxxxxx
In-reply-to: <1366404770-28523-1-git-send-email-vyasevic@redhat.com>
References: <1366404770-28523-1-git-send-email-vyasevic@redhat.com>

Doing research on another problem, I noticed that this would
break user mode spanning tree (RSTP) code.

The daemon assumes that bridge is promicious mode and therefore
will receive all link-level multicast packets.

Follow-Ups:
- Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
  - From: Michael S. Tsirkin
- Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
  - From: Vlad Yasevich

References:
- [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
  - From: Vlad Yasevich

Prev by Date: Re: [PATCHv4 net-next 2/2] bridge: Add a flag to control unicast packet flood.
Next by Date: Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
Previous by thread: Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
Next by thread: Re: [PATCH v2 net-next 0/6] Allow bridge to function in non-promisc mode
Index(es):
- Date
- Thread

[Index of Archives] [Netdev] [AoE Tools] [Linux Wireless] [Kernel Newbies] [Security] [Linux for Hams] [Netfilter] [Bugtraq] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux RAID] [Linux Admin] [Samba] [Video 4 Linux]

Powered by Linux