Node name: Powells Technical Bookstore
Live date: May 4, 2005
Contact: orb9220@gmail.com or info@personaltelco.net
Location
33 NW Park Avenue
Portland, OR 97209
Map: https://cwnmyr.personaltelco.net/nodes/PowellsTech
Equipment
- Buffalo WHR-HP-G54
Software Installed
DebianLinux sarge
OpenWrt v7.09 on Buffalo
Network Configuration
- ESSID: www.personaltelco.net
- Channel: 1
- BSSID: 00:16:01:D2:A1:FB
- Hostname: cantos
- Internet Network: 70.57.126.19
Gateway: DSL modem is NATing and handing out 192.168.1.0/24 internally. NuCab has 192.168.1.25 and is also NATing.
- Upstream DNS servers: 205.171.3.65, 205.171.2.65
- PTPnet Network: 10.11.53.1/24
Installers / Organizers
This node is managed by the NetworkOperationsTeam.
Graphs
Maintenance and System Log
- Someone needs to contact Qwest.
--- 70.57.126.19 ping statistics --- (Powell's Tech) 50 packets transmitted, 39 received, 22% packet loss, time 49297ms --- 70.57.126.20 ping statistics --- (Other hosts) 56 packets transmitted, 47 received, 16% packet loss, time 55429ms --- 70.57.126.21 ping statistics --- 40 packets transmitted, 33 received, 17% packet loss, time 39277ms --- 70.57.126.59 ping statistics --- 30 packets transmitted, 27 received, 10% packet loss, time 29205ms --- google.com ping statistics --- 50 packets transmitted, 50 received, 0% packet loss, time 49416ms
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)
Details
Portland's quintessential technical bookstore. See the website http://www.powells.com/technicalbooks for more information.
Observation Plots
