[Ewrt-devel] "Captive Portal" ...

Tue Jul 6 22:34:47 PDT 2004

Ok ... That makes sense.  The doc from the site still says:

"NoCatSplash is a Open Public Network Gateway Daemon.  It performs as a
[captive/open/active] portal.  When run on a gateway/router on a network,
all web requests are redirected until the client either logs in or clicks
"I Accept" to an AUP. The gateway daemon then changes the firewall rules
on the gateway to pass traffic for that client (based on IP address and
MAC address)."

Of course it also says:  "Anyway, this code is going to change very rapidly.
It might
not be fancy, but it should work. Comments and questions welcome."

So in reality, all that was completed is the basic redirect/agree page ...

I am really interested in modifying this code to complete the captive
portion ... And I want it to be compatible with the existing NoCatAuth Auth
Server.  I have a number of locations that are running NoCatAuth gateways
and I want to get that functionality embedded into the WRT54G ...  ;-)

Scott C. Lemon

-----Original Message-----
From: Aaron Johnson [mailto:amj at mqqn.net] 
Sent: Tuesday, July 06, 2004 11:02 PM
To: Support @ 80211.net
Cc: ewrt-devel at portless.net
Subject: Re: [Ewrt-devel] "Captive Portal" ...

 > I have been reading around, and am not sure how the "captive portal" 
works.  Where do > the user IDs and passwords come from?  In NoCatAuth 
the Auth server has these, and
 > 'pings' the gateway to tell it to allow the user.  There is then the 
'refresh' page
 > that is the 'keep alive' for the user.
 > 
 > How does this work with NoCatSplash?

NoCatSplash only implements open mode.  Anonymous "I agree" with an 
idle timeout
associated with the mac address of the client.

Aaron