netdev - Re: [PATCH RFC 0/5] net: L2 only interfaces

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:	Tue, 25 Aug 2015 17:05:46 -0700
From:	Sowmini Varadhan <sowmini05@...il.com>
To:	David Ahern <dsa@...ulusnetworks.com>
Cc:	Florian Fainelli <f.fainelli@...il.com>,
	netdev <netdev@...r.kernel.org>,
	David Miller <davem@...emloft.net>, andrew@...n.ch,
	linux@...ck-us.net,
	Jiří Pírko <jiri@...nulli.us>,
	sfeldma@...il.com
Subject: Re: [PATCH RFC 0/5] net: L2 only interfaces

On Tue, Aug 25, 2015 at 4:52 PM, David Ahern <dsa@...ulusnetworks.com> wrote:


> The VRF driver can check the device when the enslave request happens.
>

Will this work correctly if I set up a bonding interface or SVI,
and want to put the bond-master or SVI in the vrf (but subsequently
want to get, say, timestamp/other-stats from the L2 slave in the vrf?)

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