<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
All of the documentation is contained within their download. It appears
like a nice lightweight solution. It is basically a captive portal that
requires authentication before allowing access to the internet. It
takes a different approach then netreg using dynamically created
iptables generated after a user logs in. Whereas netreg uses dhcp to
assign one set of ip addresses to an authenticated group of users and
one set of ip addresses to an unauthenticated set of users. It appears
in their current implementation nocat would require an authentication
every time a user connects to the system and netreg would require a
single authentication event and subsequently would read the mac address
from the dhcpd.conf file and grant an authenticated ip address.<br>
<br>
Regards,<br>
Reuben<br>
<br>
<br>
Martin Langhoff wrote:
<blockquote
cite="mid:46a038f90904280156u2959b928nbad0fbd4159d49df@mail.gmail.com"
type="cite">
<pre wrap="">On Mon, Apr 27, 2009 at 11:34 PM, Jerry Vonau <a class="moz-txt-link-rfc2396E" href="mailto:jvonau@shaw.ca"><jvonau@shaw.ca></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Have a look at the method used with NoCatAuth from <a class="moz-txt-link-freetext" href="http://nocat.net/">http://nocat.net/</a>
Might make a good starting point.
</pre>
</blockquote>
<pre wrap=""><!---->
Looked at it briefly, but it's not clear what's interesting in it. Is
there something specific that nocat does really well?
cheers,
m
</pre>
</blockquote>
</body>
</html>