|
← Revision 1 as of 2006-04-22 11:45:37 →
Size: 690
Comment: created skeleton page for this node
|
Size: 2837
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
|
'''Node name:''' City Repair Node [[BR]] '''Live Date:''' February 2, 2002 [[BR]] '''Sponsor:''' Joe Company [[BR]] '''Contact:''' Joe Blah mailto:joe@company.com |
## page was renamed from NodeCityRepair '''Node name:''' [http://www.communitecture.net Communitecture] (503-230-1293) [[BR]] '''Live Date:''' April 29, 2006 [[BR]] '''Contact:''' RussellSenior [[BR]] |
| Line 6: | Line 6: |
|
Address [[BR]] Portland, OR Zipcode |
1639 SE 12th Ave. [[BR]] Portland, OR 97214 |
| Line 11: | Line 11: |
|
* |
* Metrix Mark I * Atheros CM9 a/b/g radio * Pacific Wireless 9dBi omni with 7-degree downtilt * Nucab |
| Line 16: | Line 18: |
|
* |
* Pyramid (on the metrix) * Standard Builder install on the Nucab |
| Line 22: | Line 24: |
|
* Channel: * BSSID: * Hostname: * Internet Network: x.x.x.x/yy (or dynamic) * Gateway: x.x.x.z * Upstream DNS servers: x.x.x.z, x.x.x.z, ... * PTPnet Network: x.x.x.x/yy |
* Channel: 1 * BSSID: 00:0B:6B:4C:B5:FB * PTPnet Network: 10.11.62.128/25 * Nucab Hostname: dryrot (10.11.62.129) * Metrix Hostname: mildew (10.11.62.130) * Internet Network: 68.178.19.227/24 * Gateway: 68.178.19.1 * Upstream DNS servers: 204.130.255.3, 64.122.32.71 |
| Line 33: | Line 35: |
|
* |
* RussellSenior * CalebPhillips * DonPark * AlexisTurner * SamChurchill * AaronBaer * Maintained by the NetworkOperationsTeam |
| Line 37: | Line 44: |
|
* |
* 2006-10-17: Responded to a call from BrianPerry indicating the node was down. I failed to see the metrix wirelessly, and we rebooted it. Then I failed to get a DHCP lease. We eventually tracked it down to a bad cat5 cross-over between the nucab and and PoE injector. I installed one of my own. In the context of fixing our external access, Brian offered to pay for a switch to be placed upstream from the Communitecture network to isoloate it from the node, as I had discussed a few months ago with Brian Garrison. * 2006-05-08: Stopped by to set up port forwarding. Discovered the DSL modem is configured to do NAT on 192.168.1.0/24, which the D-Link is connecting to. So, just port-forwarding from the D-Link isn't going to work. Have to reschedule a time when my errors won't mess them up. I also had some trouble getting DHCP resolution on my laptop. Moved dryrot to a static IP on eth0 (192.168.0.10, the dlink's dhcp range starts at 100). --RussellSenior * 2006-04-29: We need to talk to Communitecture folks, Christine in particular, about integrating with their network. Currently we are plugged into their wireless router, using iptables to disallow our wireless traffic from connecting to their LAN. Our initial preference was to put the Nucab in front, hanging their network off of eth2, and allowing us to do traffic shaping as necessary to keep them happy. The downside of that is our nucab becomes a point of failure. In any case, we didn't have administrative access to their D-Link wireless router, so we've punted for now until we can work it out with Christine. * 2006-04-29: Node is live. - CalebPhillips |
| Line 43: | Line 52: |
| * | * Install scheduled for April 29, 2006 starting at 10:30 am |
Node name: [http://www.communitecture.net Communitecture] (503-230-1293) BR Live Date: April 29, 2006 BR Contact: RussellSenior BR
1639 SE 12th Ave. BR Portland, OR 97214
Equipment
- Metrix Mark I
- Atheros CM9 a/b/g radio
- Pacific Wireless 9dBi omni with 7-degree downtilt
- Nucab
Software Installed
- Pyramid (on the metrix)
- Standard Builder install on the Nucab
Network Configuration
- ESSID: www.personaltelco.net
- Channel: 1
- BSSID: 00:0B:6B:4C:B5:FB
- PTPnet Network: 10.11.62.128/25
- Nucab Hostname: dryrot (10.11.62.129)
- Metrix Hostname: mildew (10.11.62.130)
- Internet Network: 68.178.19.227/24
- Gateway: 68.178.19.1
- Upstream DNS servers: 204.130.255.3, 64.122.32.71
Installers / Organizers
Maintained by the NetworkOperationsTeam
Maintenance and System Log
2006-10-17: Responded to a call from BrianPerry indicating the node was down. I failed to see the metrix wirelessly, and we rebooted it. Then I failed to get a DHCP lease. We eventually tracked it down to a bad cat5 cross-over between the nucab and and PoE injector. I installed one of my own. In the context of fixing our external access, Brian offered to pay for a switch to be placed upstream from the Communitecture network to isoloate it from the node, as I had discussed a few months ago with Brian Garrison.
2006-05-08: Stopped by to set up port forwarding. Discovered the DSL modem is configured to do NAT on 192.168.1.0/24, which the D-Link is connecting to. So, just port-forwarding from the D-Link isn't going to work. Have to reschedule a time when my errors won't mess them up. I also had some trouble getting DHCP resolution on my laptop. Moved dryrot to a static IP on eth0 (192.168.0.10, the dlink's dhcp range starts at 100). --RussellSenior
- 2006-04-29: We need to talk to Communitecture folks, Christine in particular, about integrating with their network. Currently we are plugged into their wireless router, using iptables to disallow our wireless traffic from connecting to their LAN. Our initial preference was to put the Nucab in front, hanging their network off of eth2, and allowing us to do traffic shaping as necessary to keep them happy. The downside of that is our nucab becomes a point of failure. In any case, we didn't have administrative access to their D-Link wireless router, so we've punted for now until we can work it out with Christine.
2006-04-29: Node is live. - CalebPhillips
Notes
- Install scheduled for April 29, 2006 starting at 10:30 am