Nodogsplash is a nocatsplash replacement derived from the WifiDog code base.

The latest version (currently 0.8beta2) now has simple traffic control permitting specification of aggregate upload and download rate limits on the managed interface.

Source tarball, .ipk package compiled against OpenWRT WhiteRussian 0.9, and documentation at http://kokoro.ucsd.edu/nodogsplash/.

Let me know of any problems (or successes for that matter).

--Paul

can you have the user redirected to a page that doesn't have the login button? ie. send them to a registration page (name/email) then they advance to the accept TOS pages and then hit the login button?

The short answer is no.

Longer answer:  If you need to have user names and passwords and the like, consider something like Chilispot or Wifidog.  Nodogsplash is intended to be much simpler than that, and with simplicity comes functionality that is really pretty limited...  Put it this way:   Nodogsplash is essentially wifidog with some functionality taken out.  Add a few features like this and you would be back at wifidog again.

--Paul

no I wasn't looking for usernames and passes, I was just going to have a php splash page that sent some imput forms (name, email, for records) to a flat text file,.

I just wanted to know if the redirect page and the page where the internet enable link are can be different

so that after their info is put into the first page, they are sent to the second, and click the link

OK I see.

Well, the first page the client sees pretty much has to be the nodogsplash splash page, which is going to be served by nodogsplash's libhttpd server.  This server is pretty simple; no php or cgi or anything.  It's just going to pipe the splash page (by default /etc/nodogsplash/htdocs/splash.html) to the client, but with some variable substitution as documented in the README.

The most important variable there is $authtarget.  When nodogsplash's server gets a request at the URL that is the value of $authtarget, it authenticates the client.

So what you could try is re-write splash.html so its button has a href to your separate php-enabled server, sending the value of $authtarget as an argument.  Then write your php page to send the user to that $authtarget URL when the user has jumped through your hoops.

That might give you something like what you want...

--Paul