Zap stands for Zone d'accès publique (public access zone) and the Zap Stack is everything necessary to run a wireless community. Wifidog is just a piece of this stack. This page is intended as a reference to help people build their community. Existing communities share what they use on their systems.

In Quebec, the Alliance des Communautés sans fil du Québec has a project to build a full stack of software tools, ready to deploy by a new community or be used by existing ones. This page is also a work base for this project, and anyone is welcome to share here.

Wireless Toronto

by gabe shawney

I dunno exactly what the Zap Stack is, but I like the idea of us sharing tips on all the stuff around WifiDog which we use to run our networks. Here's Wireless Toronto's "stack"; I hope it helps to get us started:

Gateway:

• openwrt
• wifidog
• ntpclient
• crond
• openvpn
• (for all the gory details, see  http://wiki.wirelesstoronto.ca/router_setup_instructions)

Server:

• apache+php+postgres+phppgadmin
• wifidog-auth ( http://auth.wirelesstoronto.ca/)
• wordpress (+mysql) ( http://wirelesstoronto.ca/blog/)
• mailman (+python) ( http://lists.wirelesstoronto.ca/)
• dokuwiki ( http://wiki.wirelesstoronto.ca/)
• openvpn server
• mrtg

Services:

• dns hosting at easydns.com
• IVR hosting for phone-based end-user tech support
• voip service for IVR hosting
• server monitoring

Zap stack user stories

by Alexis Cornellier and from the page TNG

• Firmware should update automatically and remotely. Even if maintenance may be necessary after update
• Wifidog config should be hosted on the server instead of on the router, so that changes can be done easily
• It should be possible to show statistics to hotspot owner so he can see the evolution of the service
• A monitoring system should be available so acces point behavior can be monitored over a long period
• a QOS system should be put in place
• 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) (see WifidogAPI for a discussion on the api)
• Doc. the stack : Auth Server (hub), Gateway (node) and CMS (api)
• Exploration of MESH and other hardware and integration with meshing protocols and management.
• Ability to group nodes in different ways (several nodes per "hotspot", serveral hotspots in a group, overlaping groups, etc.).
• Federation
• Ability to use MySQL (database abstraction)
• Reporting (to hotspot owners)