Version 7 (modified by scarle, 12 years ago)


This page is used to collect the feature requests for Wifidog The Next Generation and help organize the work related to that project.

As some of you already know, we have been drafting a plan for the next version of wifidog, dubbed WifiDog TNG (the next generation).

We organized a few conference calls with other wifi orgs (Zap Québec, Zap Sherbrooke and other upcoming ZAPs) as well as with NYC Wireless and Wireless Toronto to collect as much as input as possible and gather consensus for future direction. I (SylvainCarle) also had good one-on-one chats with Benoit Grégoire, François Proulx and the current (and past) ISF board members. This is is first draft of the objectives for wifidog 2.0

A few principles first. This is to be a process as inclusive as possible, it's open for contribution to any able and willing developer. It will be organized from the current Trac ticket system and wiki (see a copy of this email at

There is a deadline for the first 2.0 release in August as several groups will need the new features for specific fall projects. As such, some ideas might be great but not consider for inclusion in the first release. A schedule for point releases (2.1, 2.2, etc) shall be discussed here but the goal is to be consistent with stable and supported releases and an "edge" version.

Goal : make wifidog easier to integrate with other related opensource projects.

  • Be backward compatible and build on the excellent core we already have
  • Have two version, one "mini" for limited capacity hardware (as used in many existing installations worldwide, WRTG et al) and one "maxi" for more modern hardware (with much more processing power + memory)
  • Target platform: OpenWRT (Pyramid Linux as #2 and Sky OS as possible #3, we should also look at a deb/ubuntu packaging maybe)
  • Better reporting + integration with external graphing/reporting tools
  • Consolidate security patches and new ROM images
  • Support several modes: Authentification, Agreement et Content+Redirect
  • Development of a geolocation API for session/content/context
  • Integration with open source CMS for portal pages (via plugins): Wordpress is first candidate (Drupal and Pylons are considered)
  • Doc. the stack : Auth Server (hub), Gateway (node) and CMS (api)
  • Developing "Zap in a Box" for new cities/regions (make it easier to start a new wireless orgs)
  • Exploration of MESH and other hardware

We are doing a little hackfest at Arts Café in Montreal this wednesday (22nd) @ 18h30 to continue this process.

This is a lots of details, but I wanted to kickstart this process as much as possible with the tremendous community we have here. Comments, suggestions and questions are of course more than welcomed here and on the mailing list (

-- Sylvain Carle Board Member of ISF and Herder of Open Source Cats (I mean Dogs)!

I'm starting a survey of "competitive" and related software that we should consider in making architecture decisions. (can't make a new page yet, so I'm going to throw up a list of software here which I will move later).

==Portal Managment==

 Drupalfloss community CMS
 Wordpressfloss blogging CMS
 Pylonsflexible Python web framework

==Network Managment==

==Hotspot Management==