From: Brad Hards <bhards@bigpond.net.au>
To: Oliver Neukum <oliver@neukum.name>,
"Folkert van Heusden" <folkert@vanheusden.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: local link configuration daemon?
Date: Wed, 20 Nov 2002 08:15:56 +1100 [thread overview]
Message-ID: <200211200815.56896.bhards@bigpond.net.au> (raw)
In-Reply-To: <200211191827.10622.oliver@neukum.name>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Wed, 20 Nov 2002 04:27, Oliver Neukum wrote:
> Am Dienstag, 19. November 2002 18:02 schrieb Folkert van Heusden:
> > Hi,
> >
> > I just read this RFC on 'local link configuration' (mirrored at
> > http://keetweej.vanheusden.com/~folkert/draft-ietf-zeroconf-ipv4-linkloca
> >l. t xt ) and I was wondering: is this planned to be in the kernel? Or
> > should occur this in userspace? (and if so; does it exist?
> > freshmeat/google say it doesn't)
> > Initially I thought I just configure an ip-address in that range on an
> > adapter, but then I read that there is this whole protocol of sending and
> > receiving arp-requests etc.
>
> Brad Hards has done a preliminary implementation that runs in user space.
It was originally done by Sebastian Kuzminsky. It basically uses the kernel's
packet filter (BPF) and socket code, via Libnet and libpcap. You can get it
from your friendly kernel.org mirror
(http://www.XX.kernel.org/pub/software/network/zcip/, where XX is your
country code).
In the longer term, it might be appropriate to move some of it (the defend
part of the claim-and-defend sequence) into kernel space. I don't think it
makes sense to have it all in kernel space.
However since it is still an i-D, and hasn't reached RFC state, I think it is
better to work up a reference implementation in userspace, and think about
how much might need to be in the kernel (for performance reasons, whatever)
when the RFC is released and we have a little deployment experience.
Brad
- --
http://linux.conf.au. 22-25Jan2003. Perth, Aust. I'm registered. Are you?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE92qoMW6pHgIdAuOMRAsLhAJ9PBj1DyxSLfPa6JLYUPR81GKhDEwCePEYk
Aznd3lBCdznErhRgtkKNvS4=
=xz4Y
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2002-11-19 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-19 17:02 Folkert van Heusden
2002-11-19 17:27 ` Oliver Neukum
2002-11-19 21:15 ` Brad Hards [this message]
2002-11-19 22:51 ` Oliver Neukum
2002-11-19 23:10 ` Brad Hards
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=200211200815.56896.bhards@bigpond.net.au \
--to=bhards@bigpond.net.au \
--cc=folkert@vanheusden.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@neukum.name \
/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
all inboxes | Powered by JetHome®