Differences between revisions 35 and 38 (spanning 3 versions)
Revision 35 as of 2003-04-21 11:05:01
Size: 5666
Editor: pw
Comment:
Revision 38 as of 2003-08-24 21:20:44
Size: 5501
Editor: dsl081-060-155
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
 * [http://www.myzona.net/opensplash/ OpenSplash] - It utilizes Perl to manipulate ipfw rules. Apache is needed.
Right now there are not many features, for example no time limiting, no proper authentication, and rules need to be flushed manually if required. But it does its job well for now. The idea is to show a User Agreement / TOS page before anyone can access the internet.
 * [http://nocat.net/download/NoCatAuth/ NoCatAuth]
  *Written in perl, supports Linux/iptables and OpenBSD/pfctl. GPLed. Supports authenticating modes against an auth service with a wide variety of backends, including a MySQL database, PAM, RADIUS, LDAP, and more. Also features a non-authenticating "open mode" that merely requires a user to accept an AUP before they can log in. This project is more or less seeking a new maintainer.
 
 * [http://nocat.net/download/NoCatSplash/ NoCatSplash]
  *Written in C, currently under heavy development. Intended to be the successor to NoCatAuth, the gateway process and all its data files fit within 200-250k, making it ideal for embedded environments.
Line 8: Line 11:
 * [http://nocat.net/download/NoCatAuth/ NoCatAuth] -- Written in perl, supports Linux/iptables and OpenBSD/pfctl. GPLed. Supports authenticating modes against an auth service with a wide variety of backends, including a MySQL database, PAM, RADIUS, LDAP, and more. Also features a non-authenticating "open mode" that merely requires a user to accept an AUP before they can log in. This project is more or less seeking a new maintainer.
 
 * [http://nocat.net/download/NoCatSplash/ NoCatSplash] -- Written in C, currently under heavy development. Intended to be the successor to NoCatAuth, the gateway process and all its data files fit within 200-250k, making it ideal for embedded environments.
 *[http://www.cc.saga-u.ac.jp/opengate/index-e.html Opengate developed at Saga University (Japan)]
  *GPLed, runs on FreeBSD. Uses a Java applet to keep the connection open, and ftp or pop3 servers for an authentication back-end. (added by Jim Thompson)
Line 12: Line 14:
 *[http://www.cc.saga-u.ac.jp/opengate/index-e.html]Opengate developed at Saga University (Japan)
 *GPLed, runs on FreeBSD. Uses a Java applet to keep the connection open, and ftp or pop3 servers for an authentication back-end. (added by Jim Thompson)
 * MetaNet by ErikWalthinsen.
  *Still in early beta but it will provide an entire network application framework rather then just a CaptivePortal solution.
Line 15: Line 17:
 * MetaNet by ErikWalthinsen. Still in early beta but it will provide an entire network application framework rather then just a CaptivePortal solution.  *[http://www.geekspeed.net/wicap/ WiCap] by BrianCaswell
  * Written in Perl and runs under OpenBSD. I believe this is what NovaWireless will be deploying.
Line 17: Line 20:
 * WiCap by BrianCaswell - Written in Perl and runs under OpenBSD. I believe this is what NovaWireless will be deploying.
  *
http://www.geekspeed.net/wicap/

 *
River of Stars' wireless heartbeat implementation (presently most usable on an OpenBSD gateway)
  * http://www.river.com/tools/authhb/
 * [http://www.river.com/tools/authhb/ River of Stars]
 * Wireless heartbeat implementation (presently most usable on an OpenBSD gateway)
Line 38: Line 38:
 * [http://www.myzona.net/opensplash OpenSplash] by Aleksandr Melentiev from San Francisco Wireless - Inspired by the simplicity of wicap, intended to run on FreeBSD by utilizing Perl and ipfw. Doesn't provide much functionality, other than a simple AUP agreement.  * [http://www.myzona.net/opensplash OpenSplash] by Aleksandr Melentiev from San Francisco Wireless
  *
Inspired by the simplicity of wicap, intended to run on FreeBSD by utilizing Perl and ipfw. Doesn't provide much functionality, other than a simple AUP agreement.
Line 61: Line 62:
  * [http://www.nas.nasa.gov/Groups/Networks/Projects/Wireless/index.html NASA's Wireless Firewall Gateway]
    * A solution using Openbsd, PHP, IPFilter and Apache. There is no source available that I know of.
 * [http://www.nas.nasa.gov/Groups/Networks/Projects/Wireless/index.html NASA's Wireless Firewall Gateway]
  * A solution using Openbsd, PHP, IPFilter and Apache. There is no source available that I know of.
Line 68: Line 69:
    * Hack using FreeBSD, perl, ipfw and mini_httpd. No source available --MattPeterson     * Hack using FreeBSD, perl, ipfw and mini_httpd. No source available -- MattPeterson
Line 70: Line 71:
 * [http://www.birdstep.com IPzone] Linux,Apache No source available
-- Suresh Rasaretnam
 * [http://www.fatport.com FatPort]
    * Gateway software running OpenBSD, Perl, C, and Apache.
    * Auth server running PostgreSQL, etc..
    * System can be licensed, but code not available. --KenSimpson

 * [http://www.birdstep.com IPzone] Linux,Apache No source available -- Suresh Rasaretnam

Since we first started talking about using the browser as an authentication tool in December 2000 OpenSource implementations have started to appear. Here is a list of all the software I know of that implements either a CaptivePortal or an ActivePortal solution.

Open Source

Commercial or Proprietary


[CategorySoftware]

PortalSoftware (last edited 2013-08-02 12:18:46 by cable-89-216-24-221)