Differences between revisions 3 and 10 (spanning 7 versions)
Revision 3 as of 2006-04-26 22:41:58
Size: 740
Editor: DonPark
Comment:
Revision 10 as of 2006-04-29 17:41:12
Size: 1878
Comment: added some notes and info.
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
'''Node name:''' Communitecture [[BR]]
'''Live Date:''' February 2, 2002 [[BR]]
'''Sponsor:''' Joe Company [[BR]]
'''Contact:''' Joe Blah mailto:joe@company.com
'''Node name:''' [http://www.communitecture.net Communitecture] (503-230-1293) [[BR]]
'''Live Date:''' April 29, 2006 [[BR]]
'''Sponsor:''' BrianPerry [[BR]]
'''Contact:''' [[BR]]
Line 7: Line 7:
se 13th and market [[BR]]
Portland, OR Zipcode
1639 NE 12th Ave. [[BR]]
Portland, OR  97214
Line 12: Line 12:
 *
 * Metrix Mark I
  * Atheros CM9 a/b/g radio
  * Pacific Wireless 9dBi omni with 7-degree downtilt
 * Nucab
Line 17: Line 19:
 *
 * Pyramid (on the metrix)
 * Standard Builder install on the Nucab
Line 23: Line 25:
 * 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
 * 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
 * PTPnet Network: 10.11.62.128/25
Line 34: Line 36:
 *
 * RussellSenior
 * CalebPhillips
 * DonPark
 * AlexisTurner
 * SamChurchill
 * AaronBaer
 * Maintained by the NetworkOperationsTeam
Line 39: Line 46:
 *
 * 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 44: Line 51:
 *  * 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 Sponsor: BrianPerry BR Contact: BR

1639 NE 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
  • 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
  • PTPnet Network: 10.11.62.128/25

Installers / Organizers

Maintenance and System Log

  • 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


[CategoryNode][CategoryPersonalTelco]

NodeCommunitecture (last edited 2024-12-16 06:05:24 by RussellSenior)