|
Size: 1878
Comment:
|
Size: 2332
Comment: double-natting, d'oh
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 27: | Line 27: |
| * PTPnet Network: 10.11.62.128/25 | |
| Line 32: | Line 33: |
| * PTPnet Network: 10.11.62.128/25 | |
| Line 46: | Line 46: |
| * 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 |
Node name: [http://www.communitecture.net Communitecture] (503-230-1293) BR Live Date: April 29, 2006 BR Sponsor: BrianPerry BR Contact: 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-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