wrt54g

Has anyone put together a requirement spec for auth in nocatsplash ?

Currently the wrt can use :-

nocat
chillispot
wifidog

With chillispot having the radius server support etc.

I've been using nocatsplash with locustworld for a couple of years, and they
use external sh script call to validate a user/name password, but its not
without problems.

The main problem with external code is getting instructions back to nocat,
i.e. if you want to kick off a mac, you can't inform nocat. You can delete
the iptable rule, but then the nocat status tables still have that user as
validated.

I guess it depends on how secure you want the authorication process, and how
much you want nocatsplash to do.

For example, we've been looking at nocat on ewrt, and deciding if we can add
a simple pin code to the process so that for wifi cafe, someone has to get
today's pin to get access. Now I could add the pin to the conf file, and
read it on restart, but restart wipes the current status and iptables.

The other option is to add a signal handler that tells nocat to pick up a
new config/command file. i.e. on pin change, signal nocatsplash, signal
handler picks up the new pin, and stores it for login checking.

If you don't want radius inbedded then go the LW route, and call an external
script which calls wget/curl and gets a valid/not valid from an external.

I'd also be interest in signal to pick up commands... i.e. disconnect this
mac, ban this mac etc....

My issue would be working with the tpool etc as I'm not used to that
process.

Thoughts ?