From: Patrick McHardy <kaber@trash.net>
To: Linux Netdev List <netdev@vger.kernel.org>
Subject: GVRP
Date: Tue, 27 May 2008 18:10:51 +0200 [thread overview]
Message-ID: <483C328B.7040007@trash.net> (raw)
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.
next reply other threads:[~2008-05-27 16:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-27 16:10 Patrick McHardy [this message]
2008-05-27 16:39 ` GVRP Pekka Savola
2008-05-27 17:43 ` GVRP Patrick McHardy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=483C328B.7040007@trash.net \
--to=kaber@trash.net \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).