Differences between revisions 12 and 14 (spanning 2 versions)
Revision 12 as of 2002-04-21 17:34:19
Size: 2629
Editor: 239-pool1
Comment:
Revision 14 as of 2005-03-09 05:02:51
Size: 2776
Editor: 61
Comment:
Deletions are marked like this. Additions are marked like this.
Line 17: Line 17:
 * Move firewall rules to separate table (so nocat rules can ignore all interfaces but the ones specified in nocat.conf)
 * PAM support
 * Automatically determing wireless network by looking at the inside interface.

Line 24: Line 29:
 * Move firewall rules to separate table (so nocat rules can ignore all interfaces but the ones specified in nocat.conf)
Line 30: Line 35:
 * Automatically determing wireless network by looking at the inside interface.
Line 32: Line 36:
 * PAM support
Line 44: Line 47:
HyipInvestment EgoldEcurrency GetRich MakeMoney MlmAndDownlines ForexTrading WorkFromHome HomeBusiness OnlineInvesting SafeInvestment

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!

In Progress

  • Ability to display AcceptableUseAgreement via server side include from central server

  • Pop up window which allows persistent branding, logout button, node info, trouble reports etc (NoCat)

  • Bandwith limiting/traffic shaping (NoCat)

Short Term

  • Add a security notice. Explain the risks and what to do about it (and why we don't fix it).
  • Firewall rules to protect local networks (eg. "ghettowall")
  • 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)
  • 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
  • Make sure that ingress/egress filtering is done so wireless clients can't do "bad things"

Longer Term

  • Don't assume NAT
  • IPv6 support
  • 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.
  • Lots of pretty web-based administration and statistics
  • Log into a Jabber server and you're automatically logged into NoCat

  • Support remote administrative queries (via SOAP).
  • Separate management console to monitor/configure many remote nocat installations

HyipInvestment EgoldEcurrency GetRich MakeMoney MlmAndDownlines ForexTrading WorkFromHome HomeBusiness OnlineInvesting SafeInvestment

NoCatAuthWishList (last edited 2007-11-23 18:01:24 by localhost)