Diff for "NodeCrowBar" - Personal Telco Project

Differences between revisions 9 and 10

Node name: The Crow Bar, N Mississippi and Failing NodeId:565 BR Status: Fully operational BR Live Date: February 2, 2004 BR Contact: JasonMcArthur

3954 N Mississippi St.BR Portland, OR 97227 BR ["Map"]: NodeMap:NodeCrowBar

Equipment

NewCloneArmyBox
Linksys WAP54G with two 9dBi omni antennas.

Software Installed

DebianLinux sarge
NoCatAuth

Network Configuration

ESSID: www.personaltelco.net/crowbar
BSSID: 00:0F:66:18:75:0C
Channel: 1
Hostname: loki
Internet Network: 72.11.112.142 (static)
PTPnet Network: 10.11.2.65/26

Installers / Organizers

TomFitz
KeeganQuinn
JasonMcArthur
This node is managed by the NetworkOperationsTeam.

Maintenance and System Log

2007-09-02: Stopped by to determine why there was no connectivity on eth1 (to the WAP upstairs). Looked like a flakey cat5 connection at the AP end. The bartender said that when there were problems, we reseated the cat5 connection at the access point end. After the connectivity on eth1 returned, I discovered nocat was not working. I eventually traced this to tap0 being identified as one of the internal interfaces. Instead of relying on the automatic determination, I configured nocat.conf to use eth1. After that, nocat began behaving itself. --RussellSenior
2007-02-06: Stopped by to check on an outage. The eth0 interface was down. I up'd it and restarted nocatauth-gateway and it started working. --RussellSenior
2005-09-24: Upgraded to sarge. (- KeeganQuinn)

Details

Beer and wine, good food, and good solid 802.11b coverage throughout the establishment. Stop in and pick up a microbrew on tap, and play some pool or pinball.

Good selection of beer and very friendly bartenders. Open 3 p.m. to 2 a.m., 7 days a week.

Enjoy!

Observation Plots

[CategoryNode]

-  ← Revision 9 as of 2007-04-23 10:49:27 →
  Size: 2014
  Editor: cipheralgo
  Comment:
+  ← Revision 10 as of 2007-09-02 18:56:25 →
  Size: 2588
  Editor: RussellSenior
  Comment: outage fixage
-Deletions are marked like this.
+Additions are marked like this.
 Line 42:
+ * 2007-09-02: Stopped by to determine why there was no connectivity on eth1 (to the WAP upstairs).  Looked like a flakey cat5 connection at the AP end.  The bartender said that when there were problems, we reseated the cat5 connection at the access point end.  After the connectivity on eth1 returned, I discovered nocat was not working.  I eventually traced this to tap0 being identified as one of the internal interfaces.  Instead of relying on the automatic determination, I configured nocat.conf to use eth1.  After that, nocat began behaving itself.  --RussellSenior