|
Size: 2580
Comment: outage fixage
|
Size: 2780
Comment: updated information, the indoor part of the network has been unplugged for years, reflected that here.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| '''Contact:''' Chris Moehling<<BR>> | '''Contact:''' Talbot Wallace<<BR>> |
| Line 14: | Line 14: |
|
* NewCloneArmyBox (PersonalTelco) * lots of category 5 cabling (various sources) * a switch or two (unknown sources) * indoor Intel AccessPoint (Intel Corp.) * Power Over Ethernet injector for Intel AP (NigelBallard) |
* Alix 2D13 (PTP) |
| Line 25: | Line 21: |
|
* DebianLinux sarge * NoCatAuth |
* AlixCab * OpenWrt r18781 * NoCatAuth * OpenVpn * Olsrd * Snmpd |
| Line 32: | Line 31: |
|
* Channel: * BSSID: * Channel: * BSSID: * Hostname: ballista * Internet Network: 207.173.201.37/24 * Gateway: 207.173.201.1 * Upstream DNS servers: 207.173.200.225, 216.140.108.188 |
* BSSID: 00:0F:8F:9F:EF:F0 * Channel: 11 * Hostname: bow * Internet Network: 69.168.48.254/24 (a static ip provided by DHCP from Spiretech, if device changes coordination with them in needed) * Gateway: 69.168.48.1 * Upstream DNS servers: 69.168.63.194, 69.168.63.195 |
| Line 57: | Line 54: |
|
'''Is this node really an extra-large one that covers several blocks (as reported, I believe, in the Willamette Week some time ago?) If so, shouldn't the web site or at least the wiki make some mention of this point?''' |
|
| Line 61: | Line 56: |
|
* 2009-12-31: Had an outage starting 7am-ish, I think probably related to DHCP (we'd started udhcpc manually yesterday), so I stopped by to power cycle it this afternoon. The nice young woman there suggested that next time they would be willing to be our remote hands for us (and could probably do the power cycle for us). --RussellSenior * 2009-12-30: DonPark and I replaced the old NuCab "ballista" with an AlixCab "bow". Talked to Spiretech, who updated their DHCP server with our new macaddr. --RussellSenior |
Node name: Hawthorne Hosteling International
Live Date: March 9, 2002
Sponsor: Hostelling International, Oregon Council
Contact: Talbot Wallace
Website: http://www.portlandhostel.org/
3031 SE Hawthorne Blvd
Portland, OR 97214
Map: https://cwnmyr.personaltelco.net/nodes/Hawthorne
Equipment
- Alix 2D13 (PTP)
outdoor Cisco AccessPoint in case (Intel Corp.)
- unknown omni-directional antenna (Intel Corp.)
Software Installed
Network Configuration
- ESSID: www.personaltelco.net
BSSID: 00:0F:8F:9F:EF:F0
- Channel: 11
- Hostname: bow
- Internet Network: 69.168.48.254/24 (a static ip provided by DHCP from Spiretech, if device changes coordination with them in needed)
- Gateway: 69.168.48.1
- Upstream DNS servers: 69.168.63.194, 69.168.63.195
- PTPnet Network: 10.11.100.1/22
Installers
- Many more people contributed - please add your name here.
This node is managed by the NetworkOperationsTeam.
Maintenance and System Log
2009-12-31: Had an outage starting 7am-ish, I think probably related to DHCP (we'd started udhcpc manually yesterday), so I stopped by to power cycle it this afternoon. The nice young woman there suggested that next time they would be willing to be our remote hands for us (and could probably do the power cycle for us). --RussellSenior
2009-12-30: DonPark and I replaced the old NuCab "ballista" with an AlixCab "bow". Talked to Spiretech, who updated their DHCP server with our new macaddr. --RussellSenior
2009-10-14: Fixed a 12-day outage by reseating the eth1 connection at the nucab. No clicky-click though, so it's a matter of time before it happens again. Left a card and encouraged them to call next time they have an outage. Certain lack of staff enthusiasm over the node presence noted. Currently only one AP (the outdoor) is active. This could be made better with a little work. --RussellSenior
2005-10-03: Updated this page and ballista. (- KeeganQuinn)
2002-08-08 10:47 pm - It should work now. -- MichaelCodanti
2002-08-08 8:28 pm - Not able to get NoCat to redirect me to the Auth page. Can access www.personaltelco.net (right now) but cannot sign in. Recommend having a 'authenticate here' button on the home page so that when users hit the node and don't have access they know why it might not be working. - RossOlson