From: Mark Bartelt <mark@cacr.caltech.edu>
To: mlist-linux-admin@nntp-server.caltech.edu
Subject: DHCP and UAP ?
Date: Mon, 16 Oct 2006 16:58:13 +0000 (UTC) [thread overview]
Message-ID: <slrnej7eh5.d8b.mark@atlantis.cacr.caltech.edu> (raw)
I'm looking for an opensource DHCP server which supports
the user authentication protocol described in RFC 2485:
>> User Authentication Protocol Option
>>
>> This option specifies a list of URLs, each pointing to a user
>> authentication service that is capable of processing authentication
>> requests encapsulated in the User Authentication Protocol (UAP). UAP
>> servers can accept either HTTP 1.1 or SSLv3 connections. If the list
>> includes a URL that does not contain a port component, the normal
>> default port is assumed (i.e., port 80 for http and port 443 for
>> https). If the list includes a URL that does not contain a path
>> component, the path /uap is assumed.
The manpage for RHEL4's dhcpd.conf includes the following:
>> authenticated clients;
>>
>> If specified, this statement either allows or prevents allocation from
>> this pool to any client that has been authenticated using the DHCP
>> authentication protocol. This is not yet supported.
>>
>> unauthenticated clients;
>>
>> If specified, this statement either allows or prevents allocation from
>> this pool to any client that has not been authenticated using the DHCP
>> authentication protocol. This is not yet supported.
So it looks like there are hooks for this in RedHat's DHCP
server, but nothing useful (yet).
Does anyone know whether RHEL5's dhcpd will support this?
Or whether there are any other DHCP servers that I could
deploy in place of the standard RHEL4 one? Thus far, the
bit of googling I've done hasn't turned up anything useful.
Thanks in advance ...
PS: The more I think about this, though, the more confused
I am about how it would work. If a DHCP server were told to
prevent allocation from an address pool to clients which had
not yet authenticated, how could those clients even connect
to the specified authentication URLs, if they haven't gotten
an IP address yet?
I _must_ be missing something obvious here ...
---------------
Mark Bartelt
Center for Advanced Computing Research
California Institute of Technology
Pasadena, California 91125
626 395 2522
626 584 5917 fax
626 628 3994 e-fax
mark@cacr.caltech.edu
http://www.cacr.caltech.edu/~mark
next reply other threads:[~2006-10-16 16:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 16:58 Mark Bartelt [this message]
2006-10-17 11:31 ` DHCP and UAP ? Glynn Clements
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=slrnej7eh5.d8b.mark@atlantis.cacr.caltech.edu \
--to=mark@cacr.caltech.edu \
--cc=mlist-linux-admin@nntp-server.caltech.edu \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).