Node name: The Crow Bar
Live Date: February 2, 2004
3954 N Mississippi St.
Portland, OR 97227
- Buffalo WZR600DHP
- Hostname: loki
- Channel: 11
- BSSID: 10:6f:3f:7f:b0:f0
- ESSID: www.personaltelco.net/crowbar
- Channel: 40
- BSSID: 10:6f:3f:7f:b0:f1
- SSID: www.personaltelco.net/crowbar
- WAN interface: eth1
- static: 10.1.10.118/24
- Default route: 10.1.10.1
- Public interface: br-pub (eth0, wlan0, wlan1)
- IPaddr: 10.11.2.65/26
- IPv6addr: 2001:470:e962:241::1/64
Clients on the public network are administratively prevented from reaching any hosts on the private network immediately upstream.
Installers / Organizers
Maintenance and System Log
2013-12-30: There was an outage starting on Saturday afternoon, was reported by a user. When I checked this morning, I discovered that the wireless was visible, but I was not getting a DHCP lease. I did see an IPv6 route though, and was able to log in via the link-local IPv6 address and rebooted. The buffalo came back up and seems to be working again. No idea why that happened. --RussellSenior
2013-01-21: Installed Buffalo WZR600DHP (sponsored by owner) --RussellSenior
2012-11-21: Updated firmware to r34240 --RussellSenior
2010-02-17: The WgtCab (MISSNET-19) had kernel panic'd a few times in a row, decided to replace it. Dropped in a new one that we had initially prepped to go to NodeKentonStation (but haven't heard back from them, so it was available for use here). Used the image previously flashed. Had to patch up the SSID for crowbar. Otherwise, good to go. --RussellSenior
2009-07-24: Decommissioned the NuCab (which had been disconnected some time ago) as well as the AP, replaced with WgtCab. It is plugged into their private network, but we are using an iptables rule to prevent access to private network hosts from public network. --RussellSenior
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)
Beer and wine, good food, and good solid 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.