Differences between revisions 20 and 21
Revision 20 as of 2007-10-18 22:43:27
Size: 4204
Comment: add report on days activities
Revision 21 as of 2007-10-24 13:31:59
Size: 4470
Comment: reflashed communitecture
Deletions are marked like this. Additions are marked like this.
Line 45: Line 45:
 
 * 2007-10-24: Reflashed the rooftop metrix (mildew) with a pyramid-1.0b5-based image, basically a tweaked version of what we are currently using on Mississippi. Turned off the linkstat script (a missnet thing). We'll see if that improves things. --RussellSenior

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)
  • Nucab eth0 ipaddr: 192.168.1.129/24 (behind dsl modem NAT)
  • 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

Maintenance and System Log

  • 2007-10-24: Reflashed the rooftop metrix (mildew) with a pyramid-1.0b5-based image, basically a tweaked version of what we are currently using on Mississippi. Turned off the linkstat script (a missnet thing). We'll see if that improves things. --RussellSenior

  • 2007-10-18: Stopped by to help out with a router failure upstream from our gear. While there, took the opportunity to install a 5 port switch between the DSL modem and their new router, which gets us off of their internal network. We had talked about this a while back, and this was a good opportunity to do it. A call to Integra would probably get our port forwards installed too. We are still getting reports of outages there that seem to originate in the metrix. I see messages like "wifi0: stuck beacon; resetting (bmiss count 4)" and "eth0: increased tx threshold, txcfg 0xd0f01008". I really need to cobble up a new firmware image (done, but needs testing) and get it flashed (maybe tomorrow). --RussellSenior

  • 2007-08-31: Responding to reports of node outage, stopped to check. The /etc/udev/rules.d/z25_persistent-net.rules had a typo that resulted in interfaces getting the wrong names, and thus eth0 had gotten misplaced and access to the outside was lost. Corrected, rebooted, fixed. --RussellSenior

  • 2007-05-07: Responded to a call indicating the node was down. Checked the network cables, power cycled the roof in the process, node is back up. Restarted openvpn tunnel, can't ping 10.11.255.1 from a client. Not sure if that is expected or not. --RussellSenior

  • 2006-10-17: Responded to a call 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


[CategoryNode][CategoryPersonalTelco][CategoryNodeBehindNat]

NodeCommunitecture (last edited 2019-09-25 18:42:31 by RussellSenior)