netdev - GVRP

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-next>] [day] [month] [year] [list]

Date:	Tue, 27 May 2008 18:10:51 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	Linux Netdev List <netdev@...r.kernel.org>
Subject: GVRP

I've written an applicant-only GVRP implementation for the kernel
some time ago (for those not familiar: it dynamically registers
VLANs with switches. Applicant-only means its only the "client-side")
and I'm wondering whether I should merge it. It should be quite
easy to move it to userspace, OTOH I think it would be nice to
have the client-side support for this without having to install
additional daemons. But since this is not a really strong argument,
I'd like to hear if anyone has an opinion about this.

The GVRP implementation sits on top of an GARP implementation,
which could also support GMRP for multicast address registrations.

I'm not including the patch yet because it would need to be
split up and needs some minor cleanups, just for orientation, the
GARP implementation is about 600 lines of simple code, the GVRP
implementation something like 60 lines of even simpler code.

Opinions welcome.
--
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