netdev - Re: [PATCHv2 iproute2 0/3] Bridge VLAN support

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: <51376E4B.4060605@redhat.com>
Date:	Wed, 06 Mar 2013 11:26:51 -0500
From:	Vlad Yasevich <vyasevic@...hat.com>
To:	netdev@...r.kernel.org
CC:	shemminger@...tta.com
Subject: Re: [PATCHv2 iproute2 0/3] Bridge VLAN support

On 02/28/2013 03:04 PM, Vlad Yasevich wrote:
> This series adds VLAN configuration to the bridge command.  With this
> series, one can specify vlans in FDB entries as well as to configure
> VLAN configuration on the bridge ports.
>

Stephen

This wad resent after you reopened iproute2.  Did you see it?  Do you 
have any further comments?

Thanks
-vlad

> Since v1:
>   - Rebased.
>   - Call rtnl_wilddump_req_filter from rtnl_wilddump_request.  Preserve always
>     setting the RTEXT_FILTER_VF filter.
>
> Vlad Yasevich (3):
>    bridge: Add vlan support to fdb entries
>    bridge: Add vlan configuration support
>    bridge: Update bridge man pages to include vlan command
>
>   bridge/Makefile      |    2 +-
>   bridge/br_common.h   |    1 +
>   bridge/bridge.c      |    3 +-
>   bridge/fdb.c         |   16 ++++-
>   bridge/vlan.c        |  220 ++++++++++++++++++++++++++++++++++++++++++++++++++
>   include/libnetlink.h |    2 +
>   lib/libnetlink.c     |    8 ++-
>   man/man8/bridge.8    |   73 ++++++++++++++++-
>   8 files changed, 320 insertions(+), 5 deletions(-)
>   create mode 100644 bridge/vlan.c
>

--
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