http://wiki.wirelesstoronto.ca/ 2012-02-04T00:28:41-05:00 http://wiki.wirelesstoronto.ca/ http://wiki.wirelesstoronto.ca/lib/tpl/default/images/favicon.ico text/html 2012-01-06T12:50:33-05:00 admin http://wiki.wirelesstoronto.ca/routers?rev=1325872233&do=diff gw_id router# venue membership paid until router paid router reimbursed new root pw (May 30 2006) 24 24 Axis Gallery and Grill Apr 18 2007? ? ? no (no openvpn) 32 32 Cafe Taste May 23 2007? yes yes - Gabe yes 29 29 Cameron House Apr 28 2006? yes yes - Jason yes 39 39 Concord Cafe June 30 2007 yes no - pay Patrick yes 31 36 Dufferin Grove Park rinkhouse (I think?) - no yes - Gabe no 23 50 401 Richmond Cafe (INCOMING) 22 22 Fox & Fiddle Bloor Aug 8 2… text/html 2011-10-27T11:53:22-05:00 gabe http://wiki.wirelesstoronto.ca/technical_logs:st._lawrence_market?rev=1319730802&do=diff Wifidog has been emailed out lots of 5-minute outage reports, so it sounds like our rebooting problem is back. I remotely turned off wifidog just so that users aren't having to constantly log back in. Wifidog reported that the router went down on Sunday afternoon. 2 months after the last renewal -- I forgot to put it in my calendar. I went by this morning to renew. Same as ever; just three things I noticed: text/html 2011-09-15T15:35:36-05:00 gabe http://wiki.wirelesstoronto.ca/technical_logs:harbourfront_centre?rev=1316115336&do=diff A user emailed the support address describing trouble connecting. It sounded like our coverage area has shrunk. I checked, and I can't ping routers .67 or .68. (Was this ever resolved after March 28?) I emailed Juan to find out when I can go by to investigate. text/html 2011-08-06T13:47:14-05:00 gabe http://wiki.wirelesstoronto.ca/technical_logs:yonge_dundas_square?rev=1312652834&do=diff I rebooted the Linksys router, and no luck. I plugged my laptop into the modem and it couldn't find a PPPoE server. I rebooted the modem, and it started working. I intended to bring a lamp timer that would auto powercycle the whole rig every night, but couldn't find one. The modem problem is, as far as I can tell, a new one, so maybe it was a fluke. text/html 2011-08-02T09:14:40-05:00 admin http://wiki.wirelesstoronto.ca/auth_server?rev=1312290880&do=diff Auth server was returning errors on any wifidog page. (Could not allocate memory?) I restarted it and it came back fine. Auth returning errors, unable to connect to PostGres. * Postgres status was down so restart sudo /etc/init.d/postgresql-8.3 restart text/html 2011-07-20T09:23:21-05:00 gabe http://wiki.wirelesstoronto.ca/technical_logs:st._louis_bar_grill?rev=1311168201&do=diff Wifidog reported the node down, but I was able to connect to it through the VPN. Wifidog was running, but DNS wasn't resolving. I edited /etc/init.d/S50dnsmasq and changed the line that read “nameserver 127.0.0.1” to “nameserver 208.67.222.222” and then added another line below it, “nameserver 208.67.220.220”. (Those are opendns servers.) I then edited /etc/resolv.conf with those same two lines, and it started working right away. text/html 2011-07-06T09:05:10-05:00 gabe http://wiki.wirelesstoronto.ca/auto-oz?rev=1309957510&do=diff Updates May 11 2011 My service expired last night. My renew script still isn't working, but I didn't try very hard. All I did was run: curl -K curlcfg2 http://google.com -v curl -K curlcfg2 http://phc.prontonetworks.com/cgi-bin/authlogin -v curl -K curlcfg2 "https://register.prontonetworks.com/registration/Main.jsp?wispId=5338&nasId=00:1b:24:78:ab:82&tempName=selAuth&orgUrl=&userMacId=00:23:69:b3:ce:65" -v -c /tmp/cookiejar curl -K curlcfg2 -d 'username=$$$$$$$$&password=$$$$$$$$&changePassw… text/html 2011-06-24T17:06:59-05:00 gabe http://wiki.wirelesstoronto.ca/technical_logs:wychwood_open_door?rev=1308949619&do=diff Kathy emailed yesterday saying that the wifi was down. I went in today. She explained that it stopped working on Tuesday, but she was able to get her machine online by plugging it straight into the modem. I plugged everything back in the normal way, and realized that the Wychwood router had been reset: it had the PPPoE settings in it (and went online right away), but the admin password was blank, and it was using the LAN IP address 192.168.1.1, instead of 192.168.99.1 as we had set it.