| 16 | | * Captive portal which lets hotspot owners communicate with their users (custom content management). |
| 17 | | * Wifidog gateway runs on GNU/Linux server and embedded device like the Linksys WRT54G with OpenWRT. |
| 18 | | * Multi-language support: English, French, German, Spanish, Italian, Greek, Portuguese, Swedish, Bulgarian and Japanese. |
| 19 | | * Maintain the connection by checking network activity instead of a javascript window. This allows PDAs and cellphones to connect. |
| 20 | | * Users are unique and have a valid email address in order to open an account. Their privacy must be respected. You can also use a splash only page and do not ask user to create an account. |
| 21 | | * Users are able to create a working account directly from any hotspot. New users sign on from any hotspot, create their account and are granted access for 15 minutes to confirm an email. If they don't, they are disconnected. |
| 22 | | * Hotspot monitoring by two way heartbeating, so the central server always knows which hotspots are up, regardles of dynamic DNS, firewalls, etc. |
| 23 | | * Firewall has one rule to jump in, one to jump out when a connection is rejected, and one to jump out when a connection is accepted. The gateway must do its own NAT. All this allows wifidog to be integrated easily into an existing firewall configuration. |
| 24 | | * Statistics : Cumulative bandwidth usage accounting (per connection, per user, per hotspot) |
| 25 | | * Self-identification of the gateways ??? |
| 26 | | * [wiki:ContentDistributionSystem Content Distribution System] |
| 30 | | == Detailed features == |
| | 13 | === Main Features === |
| | 14 | * Captive portal which lets hotspot owners communicate with their users (through the [wiki:ContentDistributionSystem Content Distribution System]). |
| | 15 | * Wifidog gateway was designed for and runs on GNU/Linux servers and embedded linux devices, e.g. Linksys WRT54G with OpenWRT. For a current list of supported devices and installation instructions please click [wiki:doc Here]. |
| | 16 | * Multilingual support (through browser detection and user selection) with the ability to add more languages using a .po editor (please see [wiki:doc/developer/LanguageTranslation Language Translation] for more details).Current implemented languages are: |
| | 17 | * English |
| | 18 | * French |
| | 19 | * German |
| | 20 | * Spanish |
| | 21 | * Italian |
| | 22 | * Greek |
| | 23 | * Portuguese (also Brazilian) |
| | 24 | * Swedish |
| | 25 | * Bulgarian |
| | 26 | * Japanese |
| | 27 | * Maintain the client (hotspot users) connection by checking network activity through a ping command, instead of a javascript window (like used in NoCat). This allows PDAs and cellphones and other devices without a browser to connect. |
| | 28 | * Support for differing types of hotspots: |
| | 29 | * Splash Only: Users are redirected to the portal, but do not have to login in order to use services |
| | 30 | * Normal Mode: Users are unique and must have a valid email address in order to open an account. |
| | 31 | * Users are able to create a working account directly from any hotspot. New users sign on from any hotspot, create their account and are granted access for 15 minutes to confirm an email. If they don't, they are disconnected and have to sign up again. |
| | 32 | * Hotspot/node monitoring by two way heart beating, so the central server always knows which hotspots/nodes are up, regardless of dynamic DNS, firewalls, etc. |
| | 33 | * Reports and Statistics including: |
| | 34 | * 10 highest bandwidth consumers |
| | 35 | * 10 most frequent users |
| | 36 | * 10 most mobile users |
| | 37 | * Anoymised SQL data export (for academic research) |
| | 38 | * Breakdown of how many users actually use the network |
| | 39 | * Connection log |
| | 40 | * Content display and click through report |
| | 41 | * Graph on network use (per hour, weekday and month) |
| | 42 | * Individual user report, most popular nodes (by visit) |
| | 43 | * Network status information |
| | 44 | * Node status information |
| | 45 | * Registration log |
| | 46 | * User registration report |
| | 47 | * Automatic node creation (if the person creating the node has the relevant permissions and the feature is enabled. |
| 61 | | * Every hotspot can have a folder in the local_content directory. This folder can be filed by a single logo, leaving all the rest to be default content, or be completely custom (stylesheet, login page, portal page, header, etc.) |
| 62 | | * Everything in local content is templated with smarty, no problems with web designer wrecking havoc on the auth server. You can edit everything in local_content/default even if you only speak html. |
| | 61 | * Every hotspot can have a folder in the “local_content” directory. This folder can be filed by a single logo, leaving all the rest to be default content, or be completely custom (stylesheet, login page, portal page, header, etc.) |
| | 62 | * Everything in “local_content” is templated with smarty, so there is no need for a web designer wrecking havoc on the auth server. You can edit everything in “local_content/default” even if you only speak html. |
