Differences between revisions 13 and 14
Revision 13 as of 2002-01-18 16:28:18
Size: 1444
Editor: pw
Comment:
Revision 14 as of 2002-01-19 09:41:24
Size: 1725
Editor: user-uini6o4
Comment:
Deletions are marked like this. Additions are marked like this.
Line 10: Line 10:
 * Ability to logout (maybe HTML popup window?).  * Ability to logout.
Line 13: Line 13:
 * Ability to display AcceptableUseAgreement (via server side include)  * Ability to display AcceptableUseAgreement (via server side include from central server?)
Line 18: Line 18:
 * Ability to track repeat users (business' may worry about other businesses leaching off them)
 * Fix auto-logout code
 * 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.

NoCatAuth is the CaptivePortal that is being developed by the NoCat group. It is in beta right now, and will support having an open system with configurable restrictions to bandwidth and ports based on if the user is a trusted member or not. --MichaelCodanti


AdamShand and DonPark sat down and made a list of all the things they would like to see added or didn't like about NoCatAuth.

Short Term

  • Branded splash page (open and captive mode) (NodeSplashPages)

  • Ability to logout.
  • Pop up window which allows persistent branding, logout button, node info, trouble reports etc
  • 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?)

  • Allowed domains exception in initialize.fw (for ptp, easystreet etc)
  • 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)
  • Fix auto-logout code
  • 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.

Longer Term

  • Don't assume NAT
  • IPv6 support

MichaelCodanti adds:

  • Ability to set bandwidth restrictions based on time of day
  • Prevent access to local subnet from wireless side


[CategorySoftware]

NoCatAuth (last edited 2007-11-23 18:02:36 by localhost)