[Wifidog] WifiDog Deployments

[François Proulx]

Great it's nice to see that deployment isn't too hard ! I guess in the
future we might have very simplified automated scripts with only a few
parameters specific to the hotspot. Do you need help deploying hotspots this
weekend ? I might have some time to help you guys. I live close to Café
Vienne, I could do support there if they have any problem...

See ya

-----Message d'origine-----
De : Wifidog-bounces at isf.waglo.com [mailto:Wifidog-bounces at isf.waglo.com] De
la part de Alexandre Carmel-Veilleux
Envoyé : 30 septembre, 2004 21:58
À : Volunteers at isf.waglo.com
Cc : wifidog at isf.waglo.com
Objet : [Wifidog] WifiDog Deployments

Hello,

	Along with Mike, I set up WifiDog at Laika and Cafe Tribune. The
first setup was Laika using a WRT54G pre-configured by Pascal with the
Atwater library in mind. This took about 30 minutes to deploy, 5 for the
AP and 25 for the beer afterwards. The second was Tribune with another
box configured by Pascal, but this time it was a barebone OpenWRT and
WifiDog install with no configuration whatsoever. This took about half
an hour to deploy.

	In light of this, a few things stand out:

Both hotspots were using DHCP (i.e.: had a router)
Laika's AP was pre-configured with 192.168.2.xxx has local lan, this
saved a lot of trouble in that environment.

I'd like to suggest that the following "script" become standard:

nvram set wl_ssid=www.ilesansfil.org
nvram set wl0_ssid=www.ilesansfil.org
nvram set lan_ip=192.168.2.1
nvram commit

mv /etc/dnsmasq.conf /etc/olddnsmask.conf
cp /etc/olddnsmasq.conf /etc/dnsmask.conf

[Edit dnsmask.conf so that 192.168.1.* becomes 192.168.2.*]

[Insert commands to install dropbear, set the passwd, disable telnet...]

reboot

Alex



_______________________________________________
Wifidog mailing list
Wifidog at isf.waglo.com
http://isf.waglo.com/mailman/listinfo/wifidog_isf.waglo.com