Wifidog was designed as a replacement to existing captive portal solutions which we felt didn't fit the needs of next generation community groups. Specifically, we wanted both personalized and community wide content for each hotspot, no pop ups, no client software and centralized management. Mainly as a replacement for portals currently using NoCat. A lot of other vendors use WiFiDog (especially the client) as a base for their solutions.
Please see the Road Map for new features currently in development.
Most awaited features are:
User classes Bandwidth limiting per class Bandwidth limiting per router Port blocking per class Apply policies based on time of day
Auth server (Current)
Node-specific content features. Wifidog-auth has a very cool local content architecture. RSS feed support (optional, with magpierss), one feed per node (url stored in the database, works great, but no gui to edit it yet) and one network-wide RSS feed. Configuration and integration No need to set any path in the web server config files All paths are editable from the config file Quick setup: the network name, url, default RSS, and similar data are set from the config file, and will be displayed as needed throughout the system. Can import all users and passwords from a NoCat password file [WWW] More info]. Development Demo page to let people to hack on it more easily Database abstraction layer with very nice debugging features (just append true at the end of the call and you'll see the query, the results, the query plan, and the number of affected rows. Porting to another database only requires porting one file. Currently uses Postgres.) User management (end user) Users can create and activate accounts without admin intervention. The user will be granted a 15 minute grace period after signing up in order to retrieve and validate his email. Users can request that the server re-send the validation email Users can change their passwords Users who forget their username can have it mailed to them. Users who lose their password can ask the system to generate a new one and mail it to them. Email must be valid but isn't displayed in order to preserve user privacy. Users can login using either email or username Enforces (politely) that duplicate email addresses are not allowed in the database Logging and monitoring MAC address logging (in case it is a legal requirement in your country) Sends the original url before redirecting to the central server in order to allow linking on the portal page Multi-language support Script and sql execution time breakdown. Already implemented, just needs to be packaged to be usable by the templates. Reports and Statistics
Supports using backup auth servers if the primary one doesn't respond. Runtime query interface One rule to jump in, one to jump out rejects, one to jump out accepts Detects the IP address of a network interface automatically, instead of specifying it separately in the configuration file.
You can also take a look at Sourceforge Feature Requests page or add your own new requests.
本文章由 http://www.wifidog.pro/2014/12/08/5.html 整理编辑，转载请注明出处