Differences between revisions 19 and 20
← Revision 19 as of 2007-05-10 06:18:40 →
Size: 4838
Editor: RussellSenior
Comment: br0 was missing its 10.11.12.1 address
← Revision 20 as of 2007-08-23 19:01:28 →
Size: 5178
Editor: RussellSenior
Comment: added outage notes
Deletions are marked like this. Additions are marked like this.
Line 38: Line 38:
 * 2007-08-22: Node has been out since approximately August 13. Cause is a failing harddisk. Took frack home to try to repair and/or replace with a wgt+senao card. Repair hit some bumps, so worked on the replacement angle, however, the senao minipci card I had does not seem to be working at full power. Not sure why. --RussellSenior

Node name: Pioneer Courthouse Square area BR Node Info: NodeId:113 BR Live Date: February 2, 2002 BR Sponsor: SRG Partnership, Inc. - GregMooreBR Contact: NetworkOperationsTeam

The Pioneer Courthouse Square area is a large brick flatspace in downtown PortlandOregon, between SW 5th & 6th, Morrison & Yamhill.

In 2002, a node was installed, successfully unwiring the entire square. Originally, the node was sponsored by Web Criteria, then in 2003 the Portland Business Alliance took up the torch. In 2005, the Business Alliance moved and SRG Partnership, Inc. is now hosting the node.

Equipment

Software Installed

Installers / Organizers

Network Configuration

  • ESSID: www.personaltelco.net
  • Channel: 1
  • BSSID: 00:02:6F:01:85:37
  • Hostname: frack
  • Internet Network: 69.30.65.86/24
  • Gateway: 69.30.65.1
  • Upstream DNS servers: 206.26.36.34, 198.107.0.14
  • PTPnet Network: wlan0: 10.11.12.1/24

Maintenance and System Log

  • 2007-08-22: Node has been out since approximately August 13. Cause is a failing harddisk. Took frack home to try to repair and/or replace with a wgt+senao card. Repair hit some bumps, so worked on the replacement angle, however, the senao minipci card I had does not seem to be working at full power. Not sure why. --RussellSenior

  • 2007-05-10: Responded to a mail to ops that eventually got moderated through. Cacti indicates no user activity since the May 3. Checked node remotely and discovered the br0 interface didn't have an IP. down/up'd wlan0 and br0 and restarted bind9 and udhcpd. We'll see if that fixed it. --RussellSenior

  • 2007-01-20: Made some snmpd configuration changes for NodeMonitoring. Also, reduced NoCat loglevel to zero. -- CalebPhillips

  • 2006-07-06: Dropped by and removed the Linksys from the equation now the NuCab has the globally routable IP and hopefully all will be well. I would commit my changes to subversion, but it appears to be down :(. - CalebPhillips

  • 2006-06-28: Experiencing intermittent issues with Linksys borking. Upgraded Linksys to newer Firmware 1.46.02. NAT Server port 80 pointed to Node PC. Are there other ports that should be passed through? -GregMoore

    • Typically 22, 5280, 80 (all TCP) are a good start 161 and 162 (UDP) are nice too, but I guess this is moot since I will be out there tomorrow removing the part that is NATing ;). - CalebPhillips

  • 2006-06-27: Installed Cisco 678 & Linksys BEFSR11. - GregMoore

  • 2006-06-26: Went by the node and noticed that it was not getting packets out to the internet. Power-cycled the DSL modem and this fixed the problem. Wrote a littler to the GeneralList asking for someone to donate a modem that doesn't suck so bad. - CalebPhillips

  • 2006-02-02: Responded to problems. Found the DSL modem borked (an Actiontec). The modem will need to be replaced by Qwest (presumably). In the interim, I've setup a similar modem. Because I was short on time and couldn't figure out how to make the Actiontec do bridging, I've set it up as a router. This required changes to the configuration of the NuCab's external interface. When we get the replacement modem -- this might be a good time to get bridging working again. For now, everything works fine again. I've forwarded ports 22,80,5280,161,162 TCP and 161,162 UDP to the NuCab. I also updated the onsite documentation. Finally, I added an account for myself to the NuCab with my PTP SSH key, but didn't give myself sudoer access. Oh, one more thing - I noticed NoCat is confused - when you agree to the terms the default redirect takes you to: http://node113.personaltelco.net/node/113, which is a 404. - CalebPhillips

  • 2005-10-03: Security updates installed. (- KeeganQuinn)

  • 2003-05-23: Upgraded hostap driver to 0.0.3. - BrianBeattie

  • 2003-05-06: Hmmm looks like somebody forgot to update this page when they upgraded the node. Removed /sbin/poweroff, not needed and will cause the system to be unavailable requiring a power cycle. - BrianBeattie

  • 2003-04-02: Checked system /var was at ~ 80%. Ran run-parts --verbose /etc/cron.daily, logrotate and symbol update failed no disk space. Cleaned out ntpstats /var/log down to 80%. Cleaned out old NoCatAuth logs down to 64%. Cleaned out current NoCatAuth logs down to 12%. Changed /etc/cron.daily/ntp-simple to remove stats older than 2 days. - BrianBeattie

  • 2002-06-03: Updated NoCatAuth to 0.80.20020603 in /usr/local/nocat-6-3-nightly --MichaelCodanti

  • 2002-04-12: Updated NoCatAuth to nightly from 4-12-2002 with patches. (Now has a status page at: http://node113.personaltelco.net:5280/status) --MichaelCodanti

NodePioneerSquare (last edited 2013-02-27 15:00:42 by RussellSenior)