netdev - Re: AF_PACKET how to get the original netdev from a packet received from a bonded master

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: <41b516cb0704181902q646c4f9bvc34e79393ee974a3@mail.gmail.com>
Date:	Wed, 18 Apr 2007 19:02:47 -0700
From:	"Chris Leech" <chris.leech@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	chavey@...gle.com, netdev@...r.kernel.org
Subject: Re: AF_PACKET how to get the original netdev from a packet received from a bonded master

On 4/18/07, David Miller <davem@...emloft.net> wrote:

> Ok, I'll try to remember to high-priority reviewing PJ's patch
> on my next rebase of the net-2.6.22 tree which should be
> tonight or tomorrow sometime.

Thanks Dave, PJ is offline this week so I'm trying to keep an eye out
for discussions related to his various patches :-)

Just to give you an idea of our motivation around this, we're looking
at layer 2 configuration protocols implemented from user space.  As an
example Link Layer Discovery Protocol could be used to detect trunking
misconfiguration, but only if you can track that information for the
underlying interfaces of a bond.  Things like 802.1x authenticated
links in a bond would have a similar issue of needing to configure
each underlying interface before bringing up the bond, but with LLDP
there's the added fun of being able to receive updated notifications
of configuration changes from the link partner at any time.

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