Consider performing a Node name: NodeGooseHollow
Live Date: January 6, 2012
Sponsor: Goose Hollow Inn/Fehrenbacher Hof
Contact: RussellSenior <russell AT personaltelco DOT net>
1927 SW Jefferson St.
Portland, Oregon 97201
503-228-7010
http://goosehollowinn.com/
Map: https://cwnmyr.personaltelco.net/nodes/GooseHollow
Equipment
- Alix 2B3
- Meraki MR24 (x3)
Software Installed
Network Configuration
- Host: ruby (alix2 gateway)
- IPv4addr: 10.11.20.1/24
- IPv6addr: 2001:470:e962:1401::1/64
- Host: ap1.goosehollow.ptp
- IPv4addr: 10.11.20.2/24
- Channel: 1
- Interface: wlan0
- SSID: www.personaltelco.net/0
- BSSID: 00:27:22:38:2d:54
- Interface: wlan0-1
SSID: GooseHollowInn
- BSSID: 02:27:22:38:2D:55
- Interface: wlan0-2
SSID: FehrenbacherHof
- BSSID: 02:27:22:38:2D:56
- Host: ap2.goosehollow.ptp
- IPv4addr: 10.11.20.3/24
- Channel: 11
- Interface: wlan0
- SSID: www.personaltelco.net/1
- BSSID: 00:27:22:38:2D:6B
- Interface: wlan0-1
SSID: GooseHollowInn
- BSSID: 02:27:22:38:2D:6C
- Interface: wlan0-2
SSID: FehrenbacherHof
- BSSID: 02:27:22:38:2D:6D
- Host: ap3.goosehollow.ptp
- IPv4addr: 10.11.20.4/24
- Channel: 1
- Interface: wlan0
- SSID: www.personaltelco.net/1
- BSSID: 00:27:22:38:2D:78
- Interface: wlan0-1
SSID: GooseHollowInn
- BSSID: 02:27:22:38:2D:79
- Interface: wlan0-2
SSID: FehrenbacherHof
- BSSID: 02:27:22:38:2D:7A
Installers / Organizers
Maintenance and System Log
2024-03-19: Got a call indicating the AP in the Goose was out since a day earlier. Went by with Ted to investigate. AP1, the upstairs AP in FehrenbacherHof had been out for a while, which was mitigated by the fact that there was another AP inside the same building. Found that the LED on the PoE injector for AP1 was dark, so we replaced the PoE injector. We inspected AP3, the AP in the Goose, and the LEDs on it looked weird. We tried power cycling it, and it looked like it almost started working but the power and ethernet LEDs were dark. I thought it might need to be replaced and we didn't have a ladder. So, we retreated. With a better idea of what might be wrong, we returned in the evening and tried swapping the remaining original PoE injectors, and OMG, AP3 started working again. I concluded that the PoE injector for AP3 was marginal. However, we were going to have trouble fitting all the AC adapters into the available power strip, so instead of having three PoE injectors and a switch, I replaced it with a PoE switch, a Zyxel GS1900-10HPv2, which I had in stock and had prepped for the contingency. We plugged it in and it WORKED. So, I spent a few minutes reorganizing the wooden backing board, decommissioning the old switch and the dying PoE injectors and replacing it with the switch. Ted and I got the switch ports organized, they are in sequence with the gateway and APs, port 1 goes to the gateway, port 2 through 4 go to AP1, AP2 and AP3, respectively. The APs were switched out for MR24s a long time ago. --RussellSenior
2013-01-31: Updated alix2 to r35318 with linux kernel version 3.7.4 and IPv6. --RussellSenior
2012-12-10: With help from Jason Clark, installed the third AirRouter, this one in the Goose Hollow Inn proper, which gets decent coverage inside for the first time. Turns out there were three unused ethernet runs between the buildings. We tested the run, it worked, I crimped a run from the attic into the bar space and it works. One shortcoming for now, the third AP is plugged into one of the LAN ports on ar0 in the office in the Hof. If ar0 flakes out, it can take ar2 with it. I suggested I bring over a netgear switch to alleviate this. Jason mentioned the office is going to be getting some remodelling. --RussellSenior
2012-01-06: Installed today, discovered the AirRouters don't like more than one of their LAN ports used at a time, probably a configuration bug, will investigate. Also, will look into getting another AP in the Goose. Currently both are on the 2nd floor of the Hof. There is a cat5 run over to the Goose, with some apparently unused pairs. We would need two pairs to make it work. --RussellSenior