Wireless Toronto technical_logs

technical_logs:215_spadina

2007-09-06T14:26:43-04:00

We got a few reports of “access denied” messages, so yesterday I tried upgrading wifidog. The new version wouldn't take, 'cause it needs a new version of OpenWRT. So I swapped in router #73 in place of router #215. Auth was reporting the (1st floor) node as down. The wifidog gateway had crashed. Gabe restarted it.

technical_logs:401_richmond

2011-05-27T17:57:49-04:00

Ali phoned again today, saying that the POS stopped working soon after I left yesterday. (I had forgotten to disable wifidog on startup.) I already had a new router with me (with a “broken bridge” -- info on how to set that up is now on the router setup instructions page on this wiki), so I popped by and installed it. I had forgotten that Beanfield locks DHCP to the MAC address, so I had to change the MAC address of the WAN interface (instructions below). All working now.

technical_logs:69_vintage

2009-05-29T10:42:10-04:00

69 Vintage had been reported down for, like, 2 months. I (Gabe) dropped by, could connect to the router but not to the Internet (though I _could_ ping the Internet). I rebooted the router (uptime of 63 days) and it came right back.

technical_logs:alternative_grounds

2010-09-23T12:08:33-04:00

Gabe got a call yesterday from Brenda saying that the wifi's been down for a few days. Wifidog reported it up, and I was able to ssh in -- everything looked ok. I phoned Brenda back, but she wasn't sure what was wrong with it; she doesn't use the wifi. She passed me to one of the servers, who said that people weren't able to find the 'wirelesstoronto' ssid. I said I'd have to come in to check it out.

technical_logs:auth_server_certificate

2009-05-29T10:42:10-04:00

From Rob: done ... here's what i did ... renewed cert at godaddy (had to call in). renewed using original csr (cert request) so i didn't have to regenerate the cert key and info. installed on auth.wirelesstoronto.ca, /etc/apache2 ... moved old cert to /etc/apache2/ssl/expired-20070408, dropped new cert and new intermediate bundle into /etc/apache2/ssl

technical_logs:axis_gallery_and_grill

2008-06-11T14:51:39-04:00

I (Gabe) got a call from the owner on my cellphone; he was getting the “Oops, can't connect to the Internet” page from wifidog. The auth server was reporting that the router had been down for over 5 days. I had him powercycle the router, and after a fairly long wait it came back up.

technical_logs:buff_nail_lounge

2007-09-21T16:31:45-04:00

Installed by Gabe. The WT router is on the front desk, plugged into their existing router. #office computer TrustedMACList 00:11:50:65:7C:BB

technical_logs:cafe_taste

2008-06-12T17:32:31-04:00

Occasionally their network screws up and they switch stuff around trying to get their credit card machine working. When they lose faith in their DLink router, they want to be able to switch everything over to the Linksys router, but then the credit card machine doesn't work. So I whitelisted it.

technical_logs:cameron_house

2009-05-29T10:42:09-04:00

On 2/8/07, Dave Robertson wrote: " Today, Cameron House, 5:30pm - router was unplugged from power & ethernet - iMac ethernet plugged directly into the cable modem - they are preparing for a show and the place was packed (luckily they all broke for dinner), “Micheal” was not there. - I plugged in the router and wired things “properly” - I tested the iMac and it was online (and whitelisted) - I tested wireless and got the login page - There is/was/is NO signal what-so-ever from downstair…

technical_logs:concord_cafe

2009-05-29T10:42:09-04:00

I was in the neighbourhood, so I stopped by Concord Cafe, since their node was reported on the auth server as being down for two months. Bell “upgraded” their DSL connection, and gave them a fancy new modem+router+wifi (it's white and thin, kind of like an airport extreme). That device had detected the presence of another router on the network and had, essentially, disabled it. Users who logged into wirelesstoronto would see the portal page, but from then on all HTTP requests would be routed …

technical_logs:dufferin_grove_park

2011-01-10T20:28:38-04:00

Jutta emailed a couple of days ago saying that stuff's down. Michael went by, rebooted the gear in the kitchen using the powerbar behind the fridge, and it all seemed to come back fine. On Nov 5 both wifidog and open-mesh reported that the routers at DGP were down. Gabe contacted the folks at the park via email, and they confirmed that while they were moving the computer, they ran into equipment trouble. The power supply for the wimax modem broke again, and Rogers refused to replace it (inst…

technical_logs:east_side_marios

2011-02-06T23:57:43-04:00

Wifidog reported that the node's been down for a while. Only 127.0.0.1 was in /etc/resolv.conf, so I did what the instructions below said and it started working. Wifidog reported that the node is down. I was able to ping it via OpenVPN ('ping 192.168.222.77' from the auth server), so I sshed in (ssh root@192.168.222.77' from the auth server), and ran 'wdctl status'. It took a long time to run, and came back saying that the wifidog gateway doesn't have Internet connectivity. When I'…

technical_logs:fox_and_fiddle_wellesley

2009-07-16T18:02:02-04:00

Gabe installed this router last night. Coverage on the main floor is weak, but on the 2nd and 3rd floors and on the patio it's fine.

technical_logs:grapefruit_moon

2010-09-29T17:10:44-04:00

They got a new POS, and whoever installed it stole the working Ethernet port. I plugged the POS into our router and whitelisted it (00:03:81:e5:ba:ae). They emailed because they had to unplug the wifi router in order to get their POS machine working. I whitelisted it (00:0b:4f:52:e5:50) in /etc/wifidog.conf and now it's working.

technical_logs:gusto_cafe

2007-01-12T16:42:27-04:00

Installed by Gabe. At the end of /etc/wifidog.conf: #office computer TrustedMACList 00:50:ba:e7:de:de Custom NVRAM settings: nvram set wl0_txpwr=1 This is to reduce signal strength; it's as low as it'll go.

technical_logs:harbourfront_centre

2011-09-15T15:35:36-04:00

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.

technical_logs:lettieri_front_east

2009-11-14T15:27:53-04:00

Need to add the register to the white list so that the owner leaves our router alone. It is being timed out and he needs to login to get online and do sales. New system? # this is for the register, which uses net connection (+VPN) to speak to Lettieri mothership TrustedMACList 00:08:9b:b1:2f:10 Kiosk is no longer present, MAC removed

technical_logs:minibar_and_patio

2007-11-25T16:11:21-04:00

Minibar is open after 7pm Voicemail may/not be listeded to. Use info@minibarandpatio.ca as primary email, typically answered by April Cooke. January 7, 2007 The powerbar that our router is plugged into was turned off. Michael P turned off the Rogers modem, powered up the router and then the modem -- everything came back online as expected. April Cooke (manager) confirmed that she doesn't need to login as her iBook had been previously whitelisted.

technical_logs:rice_bar

2010-02-09T20:11:48-04:00

Brock emailed to say that something's wrong with the Linksys router: that he can't get his desktop online unless he plugs it straight into the modem. (This explains why wifidog has been reporting frequent outages for that node for the past week or so.) I went by, checked the connections, and everything was working (without my doing anything).

technical_logs:router_troubleshooting

2009-05-29T10:42:10-04:00

Generally speaking Reboot it. If you feel like it, note what state the router is in first (wifi on, can ssh in, etc.). RECORD WHAT YOU DO in the Technical Logs. Channel conflicts If there are many networks using the same wifi channel, it can make it tough for people to see and/or use ours. Use a stumbler (iStumbler or MacStumbler for Mac, NetStumbler or one of many others for Windows) to see what other networks are around, and note which channels they're on. Generally it's best to only us…

technical_logs:router_troubleshooting_checklist

2009-05-29T10:42:09-04:00

* is the wifi network visible? * if so, can I connect to it and get a DHCP IP address? * if not, set a static IP address on your machine, i.e. 192.168.1.99 * if so, can I get online? (do I see the login/portal pages?) * if not, can I ping the router (192.168.1.1)? * if so, can I ssh into the router? * if so, is the router online? * (does it have a wan ip address?: “ifconfig”) * (can I ping the Internet?: “ping 4.2.2.2”)

technical_logs:sierra_grill

2009-07-15T13:52:38-04:00

At George's request, Gabe went by today to switch the wifi router from the Rogers modem to the new Bell modem. The Bell modem hadn'e yet been installed. I confirmed that the wifi coverage is good, and that the connection from the wifi router to the back office is reliable -- the flakiness appears to be coming from the Rogers service. Bell technicians are coming in to set up the service, and everything will get flipped over to that -- hopefully that will be the end of the problems they've been…

technical_logs:sneaky_dees

2008-04-13T12:56:39-04:00

George phoned Gabe: Rogers suspended their account because there was a high volume of spam being sent... probably from an infected machine. George called someone in to confirm that their office Windows machine isn't infected. When George told Rogers that they're running a wifi network, Rogers said that they wouldn't re-enable the connection until he WEP-encrypted the wifi. George explained to them that it's a public service for their customers; Rogers stood with their position.

technical_logs:st._lawrence_market

2011-10-27T11:53:22-04:00

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:

technical_logs:st._louis_bar_grill

2011-07-20T09:23:21-04:00

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.

technical_logs:the_3_brewers

2011-03-26T13:47:08-04:00

Same thing again. 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.

technical_logs:the_carrot_common

2011-05-10T18:18:55-04:00

A couple of days ago someone emailed asking about the node; he seemed to be in touch with the Carrot Common folks. Today at around 3pm the node came back up (after being down for a *really* long time). I inquired with the person who emailed; he said that Dan from the Carrot Common “plugged it back in.”

technical_logs:wychwood_open_door

2011-06-24T17:06:59-04:00

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.

technical_logs:yonge_dundas_square

2012-04-30T11:13:48-04:00

I got an open-mesh email notification on Apr 8 that the network went down. I dropped by a couple of times between then and now to ssh into and reboot the gateway router, but it didn't fix anything. (The problem was with the NS2.) Today I got an email from Laura at YDS, and she confirmed that she could let me into the TO Tix booth. I installed a timer which will reboot everything (NS2, Linksys router and DSL modem) every morning at 3:30ish. Once I installed it and powered everything back on, the …