Here is the wish list of things that Personal Telco would like to see added to NoCatAuth. We're working on them as we have time, energy and inspiration.
See also: NoCatAuth, NoCatAuthTesting, NodeSplashPages
Done!
- Fix auto-logout code
- Fix defunct process problem (One created for each Permit/Deny)
- Allowed domains exception in initialize.fw (for ptp, easystreet etc)
Capture requests directly to the gateway's IP (i.e. http://10.11.12.1/)
- Ability to logout (in captive/passive mode)
In Progress
Branded splash page (open and captive mode) (NodeSplashPages)
- Pop up window which allows persistent branding, logout button, node info, trouble reports etc
Short Term
- Move firewall rules to separate table (so nocat rules can ignore all interfaces but the ones specified in nocat.conf)
Ability to display AcceptableUseAgreement (via server side include from central server?)
- Firewall rules to protect local networks (eg. "ghettowall")
- A way to put up a maintenance message (eg. we're working on stuff, come back later)
- Put a link to a CGI script in the popup nav window which updates the maps server with a "last accessed on xxxxx" message.
- Ability to track repeat users (business' may worry about other businesses leaching off them)
- By desing, should not effect traffic on any interfaces but ones listed in nocat.conf. All other options should have a setting to either deny all or allow all.
- Watchdog function - a selftest every 5 mins
- Automatically determing wireless network by looking at the inside interface.
- Make sure that ingress/egress filtering is done so wireless clients can't do "bad things"
Longer Term
- Don't assume NAT
- IPv6 support
- Bandwith limiting/traffic shaping
It already does this to some extent. --MichaelCodanti
- Ability to set bandwidth restrictions based on time of day
- Custom permissions/bandwidth setting on a per user basis
- connect to centralized user/node(gawd?) database