This is an old revision of the document!
====== July 18, 2010 ====== It went down again at about 7am yesterday. I rebooted the wt-yds (Linksys) router (because I haven't yet figured out how to reset the pppoe connection), and it came back up. ====== July 16, 2010 ====== The open-mesh dashboard reported that the gateway and security routers went down on Wednesday (and the infobooth 3 days ago). I couldn't ping the linksys router via vpn. I went by today and could connect to the linksys router wirelessly. It had no 'net connection. I tried ifdown ppp0; ifup ppp0 and it didn't seem to work (or maybe I got impatient). I rebooted the router (from the commandline) and when it came back up everything seemed fine. Wouldn't it be easy to put a cronjob on to reboot (or reset pppoe) if it loses connectivity? ====== June 30, 2010 ====== The dashboard reports that all nodes went down 8 days ago. I went to the square and tried to connect to the Linksys router (ssid wt-yds), the one that handles the PPPoE connection. I was able to connect to it, but not get online. I reset the PPPOE connection (ifdown ppp0; ifup ppp0) and the Internet connection came up. I then tried connecting to the mesh router, and it worked, but I got an IP address from the Linksys router. Apparently the dhcp server in the mesh router wasn't working; presumably 'cause it knew that the Internet connection was down. I disconnected and reconnected a bunch of times, and eventually (3 minutes?) it started working like normal. My guess is that when it knows that it's offline it goes into wacko mode. As soon as it realized that it was back online again, it fixed everything. The security node came up a few minutes later. The infobooth node hadn't come up at the time that I left the square. ====== June 7, 2010 ====== The open-mesh dashboard reports that the infobooth router went down 200 days ago, the security booth router went down 129 days ago, and that the main router went down 11 days ago. The main (Ubiquiti) router was dangling; presumably the mount doesn't stick as well to the red vinyl they installed. I re-stuck it. I ssh-ed into the Linksys router and couldn't ping the 'net. I rebooted the router and it and the Ubiquiti router came back up. The Linksys router has wifi enabled, on a hidden but not secure network called wt-yds, on channel 1. I moved the mesh to channel 11. I power-cycled the router in the security office and it came back up. The router in the infobooth was unplugged; I asked them to plug it back in, and it came back up too. ====== November 11, 2009 ====== The security booth router never came back up, so I swapped in a new router. It's up now. ====== August 21, 2009 ====== Open-mesh reported that the nodes stopped checking in yesterday morning. I assume that the problem was the bad upgrade that went out through the open-mesh updating system. I swapped in the spare NanoStation2 that I'd prepared last week, and the new router and the infobooth router came up. The security booth router hasn't yet (a couple of hours later). Maybe it got the bad upgrade too? ====== August 12, 2009 ====== Gabe went by, prepared to replace each piece of equipment. But all I did was reboot the Linksys router, and the network came right back up. The only weird thing I noticed was that the spring clip that attaches the Linksys router to the column is too strong, and was squishing the router. There's ongoing work happening at the TO Tix office, so there may be some disruptions over the next few days relating to that. It would be good for us to swap the current DSL modem with one that's preconfigured with a PPPoE client -- that way we could get rid of the Linksys router. ====== July 31, 2009 ====== The open-mesh dashboard was reporting that the network was down. Alex went to reboot stuff, but couldn't get it back up. Alex went back in the afternoon to install a roach coach, and that only stayed up for a few minutes. ====== June 10, 2009 ====== Alex and I went to Dundas Square this morning to install an open-mesh network. We put a NanoStation2 at the T.O. Tix office (where the existing Linksys router is), and an open-mesh MR3201A at each of the security office and the infobooth at the south-west corner of the square. The NS2 doesn't do PPPoE, so the WRT54GL is still there, between the DSL modem and the NS2. ====== April 7, 2009 ====== Wifidog reported the node being down for a few days. They're doing some renovating and the router had simply accidentally been unplugged. The work's not done, so it might happen again... ====== January 6, 2008 ====== Wifidog reported that the spot has been down for over two weeks. Gabe went by -- the router was working, but the it couldn't ping the net. I restarted it and it came right back. ====== April 14, 2007 ====== Gabe dropped in. It's the phone cable that was broken; possibly chewed-through by someone's dog. I replaced it with another phone cable -- it's way longer than it needs to be (the only one I had on me). We can/should charge YDS for the cable. I also changed the channel to 6, since it seemed to be the least busy. ====== April 13, 2007 ====== Jeff(?) from TO Tix left a voicemail message saying that one of our cables (network or phone; it's unclear from the message) "broke"; "is in two pieces". ====== April 2, 2007 ====== Michael P. swapped in a new DSL modem on March 30, and the node has been stable since then. The modem he swapped in was from Dufferin Grove Park. He has the one that he swapped out, and will test it at his house to determine if it's defective. ====== February 8, 2007 ====== The router has recently gone into flake mode for no apparent reason. A reboot seems to fix it but it's not a long lasting cure. Michael P rebooted the machine Feb 8, 2008. T.O.Tix guy said that David (blonde?) had done the same on the 7th and Gabe on the 6th. Hotspot had been down for 16 hours when it was rebooted. ====== February 7, 2007 ====== On 2/8/07, Dave Robertson wrote: > > > Yesterday, Wednesday, Yonge & Dundas square, 5:30pm > - I power cycled the modem and it didn't seem to come back (I may have been > impatient) > - I then power cycled the router aswell, and everything came back. > - It went down again around 9:00pm :( > - It was back up today (I don't know if someone helpdesk it) > - It's down again today about 5:30pm >
