|
Size: 811
Comment:
|
Size: 1210
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 8: | Line 8: |
|
'''Short Term''' * Branded splash page (open and captive mode) |
|
| Line 9: | Line 11: |
| * Move firewall rules to seperate table? |
* Pop up window which allows persistant branding, logout button, node info, trouble reports etc * Move firewall rules to seperate table (so nocat rules can ignore all interfaces but the ones specified in nocat.conf) |
| Line 11: | Line 14: |
|
* Allowed domains exception in initialize.fw (for ptp, easystreet etc) * Firewall rules to protect local networks (eg. ghettowall) '''Longer Term''' |
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)
- Ability to logout (maybe HTML popup window?).
- Pop up window which allows persistant branding, logout button, node info, trouble reports etc
- Move firewall rules to seperate table (so nocat rules can ignore all interfaces but the ones specified in nocat.conf)
Ability to display AcceptableUseAgreement (via server side include)
- Allowed domains exception in initialize.fw (for ptp, easystreet etc)
- Firewall rules to protect local networks (eg. ghettowall)
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