Node name: Powell's Technical Books
Live date: May 4, 2005
Contact: info@personaltelco.net
40 NW 10th Avenue
Portland, OR 97209
http://www.powells.com/technicalbooks Map: https://cwnmyr.personaltelco.net/nodes/PowellsTech
Equipment
- Netgear WGT634U (on indefinite loan)
Software Installed
Network Configuration
- Hostname: cantos
- ESSID: www.personaltelco.net
- BSSID: 00:0f:b5:3f:20:d2
- Channel: 1
- WAN interface: eth0.1
- Static:
- IPaddr: 192.168.0.2
- Default route: 192.168.0.1 (DSL modem with IPaddr: 97.120.175.16, port forwarding ssh, et al.)
- DNS: 4.2.2.1 4.2.2.6
- Static:
- Public interface: ath0
- IPaddr: 10.11.0.193/26
- Private interface: eth0.0 (unused)
- IPaddr: 192.168.2.1/24
Clients on public network are administratively prevented from accessing hosts on private network.
Installers / Organizers
This node is managed by the NetworkOperationsTeam.
Graphs
Experimental status page: http://cantos.personaltelco.net/client.html
Maintenance and System Log
2011-08-31: Learned this morning that Powell's is "going a different direction with wifi access". We are looking into getting our gear back. --RussellSenior
2011-05-27: As of a couple days ago, this node is temporarily unplugged, likely for a few weeks until my contact gets back from vacation. I was told by the guy at the counter that they had unplugged both wifi networks (along with the one in the other building) for some kind of legal reason. No other information available at the moment. I have temporarily reset the SSID to www.personaltelco.net/unplugged. --RussellSenior
2010-09-27: Node was moved to a new retail location. It should be open for business on Wednesday or Thursday, across the street to the east of the main store. The rental terminals operated by Powells have been eliminated. --RussellSenior
2009-07-22: During WeeklyMeeting20090722, a group of volunteers decommissioned the NuCab and AP and installed a WgtCab in their place. The DSL modem here is still suspect, some infrastructure upstream is also a possible cause. In the case the DSL modem is replaced, it is possible to plug the existing wired machines into the WgtCab safely, since they are on an isolated private network. This would also have the advantage that we could tell if occasional slowness was the result of wired traffic. --RussellSenior
2009-01-13: Stopped by tonight to check on the outage. Looks like it might have just been a bad ethernet connection between the nucab and the DSL router. By the time I got the box pulled out to look at it and replug a few cables, everything was fine again. Will keep an eye on it. --RussellSenior
2009-01-10 - There have been reports of this node being unresponsive at times. I looked at it yesterday and from what I could tell it's upstream. Either on Powell's network, or Qwest. RussellSenior is currently working with Powell's Tech on the problem.
2007-10-11: Another report of node downage. Turns out the ac adapter had failed. It is kind of hard to find variety, so we are replacing with an access point I have on the shelf, a Buffalo WHR-HP-54G with OpenWrt v7.09. I have configured it with all the rj45 jacks bridged together so that we don't have any confusion on where the cat5 should attach. Dnsmasq and firewall scripts are disabled. Plugged in and working. --RussellSenior
2007-10-05: Linksys access point has been reset, beaconing "linksys", so I've stopped by to reconfigure it. Reconfigured, set password, set linksys ipaddr to 10.11.53.2. Seems to be working. --RussellSenior
2007-02-07: Dropped in to do some work. Noticed they had these sweet "how to use the node cards". Put the Powells Tech logo on the splash page and removed broken links from default redirect. PowellsTech++. -- CalebPhillips
2006-08-08: Received a message indicating the node was down as of Friday. Can log in to NuCab from outside. Investigating. Hmm. I can't ping 10.11.53.2, which is usually where the AP would live. Could have its power or network unplugged. --RussellSenior
2006-03-27: Responded to call for help (on ops list), found that DSL modem is new and is doing NATing which has confused the NuCab (which was configured with a static globally routable IP on the wan-side). Everything else seems to be working fine. Configured the NuCab to use 192.168.1.25 WAN-side (192.168.1.2-22 is DHCP lease range from the modem) and port forwarded some ports to it. -- CalebPhillips
2006-01-03: There's definitely something wrong with the DSL here. I'm trying to do a routine update on the system and can't make a single successful outgoing HTTP connection. I got in just fine via OpenVPN tunnel from cornerstone, and the latency is alright, but connections are just simply not working. Very strange. (- KeeganQuinn)
2005-10-13: RobertPeterson replaced the (faulty) AP. KeeganQuinn and I provided minor assistance. - CalebPhillips
2005-10-02: Responded to a problem report. The captive portal system seems fine but it sounds like the AP might need to be replaced. Security updates installed. (- KeeganQuinn)
2005-09-26: Upgraded to sarge. (- KeeganQuinn)
Observation Plots
