Differences between revisions 13 and 21 (spanning 8 versions)
Revision 13 as of 2002-01-18 16:28:18
Size: 1444
Editor: pw
Comment:
Revision 21 as of 2002-01-24 00:10:48
Size: 2107
Editor: dynamic-147-104
Comment:
Deletions are marked like this. Additions are marked like this.
Line 6: Line 6:
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. 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. (SchuylerErle updated it to reflect the current nightly.)

'''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)
Line 10: Line 15:
 * Ability to logout (maybe HTML popup window?).  * Ability to logout.
Line 13: Line 18:
 * Ability to display AcceptableUseAgreement (via server side include)
* Allowed domains exception in initialize.fw (for ptp, easystreet etc)
 * Ability to display AcceptableUseAgreement (via server side include from central server?)
Line 18: Line 22:
 * 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"
Line 22: Line 31:

MichaelCodanti adds:
 * Bandwith limiting/traffic shaping
  * It already does this to some extent. --MichaelCodanti
Line 25: Line 34:
 * Prevent access to local subnet from wireless side

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. (SchuylerErle updated it to reflect the current nightly.)

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)

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?)

  • 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
  • Ability to set bandwidth restrictions based on time of day


[CategorySoftware]

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