|
Size: 6679
Comment: added plan for NodeFreshPot link.
|
Size: 7116
Comment: added a todo item
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| * Add StephouseNetworks Logo to Buick's NoCatSplash page (as discussed at WeeklyMeeting20060104) | |
| Line 27: | Line 28: |
| ||<|4>Commons ||<|3>SE corner||<|2>Metrix ||<|2>br0(eth0,ath0,ath1)/10.11.104.5 ||wifi0/165(wds to naya-sw,west) || 8 dBi 802.11a omni || | ||<|3>Commons ||<|2>SE corner||<|2>Metrix ||<|2>br0(eth0,ath0,ath1)/10.11.104.5 ||wifi0/165(wds to naya-sw,west) || 8 dBi 802.11a omni || |
| Line 29: | Line 30: |
| ||<|1>Cisco ||BVI1({{{Dot11Radio0}}},{{{FastEth0}}})/10.11.104.6 ||{{{Dot11Radio0}}}/11 ||9 dBi 120deg pointing SE || | |
| Line 77: | Line 77: |
| ||<|1>10.11.104.16 || bridge || {{{00:0e:2e:3c:4b:88}}} || | ||<|1>10.11.104.16 || bridge || {{{00:0E:2E:3C:4B:88}}} || |
| Line 81: | Line 81: |
|
Note: When removing cisco-commons, we clipped off the ethernet and wrapped the severed end in tacky-tape. The cisco-specific PoE wiring was accomodated using an adapter section inside the enclosure. The severed tip was wired (I think) normally: * white-orange * orange * white-green * blue * white-blue * green * white-brown * brown When opening the enclosure, there was a notable scent of cooking electronics. Not overpowering, but I noticed it. --RussellSenior |
Mississippi Network Diagram and Configuration
A nucab named "mississippi" serves DHCP and does NAT for our DSL line. All of the metrix boxes run ["STP"]. The whole network is bridged, and in the 10.11.104.0/22 network.
We have MississippiMonitoring with Cacti: http://buick.personaltelco.net/cacti/graph_view.php
Include(MississippiNetworkNews, "NEWS", 2, from="^.*$")
TODO
Add StephouseNetworks Logo to Buick's NoCatSplash page (as discussed at WeeklyMeeting20060104)
- Check polarization on metrix-ed's 11a antenna (should be same as metrix-naya-sw).
- Try repointing metrix-ed's 11a antenna at metrix-commons. If successful:
- Repoint metrix-naya-nw's 11a antenna at metrix-commons; and
- Replace metrix-naya-sw with the Commons cisco.
- The Sector antennas on Naya might benefit from being repointed...
Install link to additional upstream internet connections (NodeFreshPot) and BlackRoseCollective and setup round-robin load balancing. The edimax device we'd like to use will only do bridging (not routing) in client-mode with the default (is there an alternative? so far, no) firmware. So the idea at NodeFreshPot is to install a third NIC in the NodeFreshPot nucab and give it a missnet address, string ethernet to the front of the store and connect the edimax there to one of the naya b/g radios. Need to coordinate with Tyler on that. We might need a device with more flexibility (OpenWRT?) for BlackRose.
- Need to install a "repeater" at Amnesia brewing inside and behind the corrogated steel.
- What's the deal with Broadcom-based client devices connected to Atheros based APs? Why doesn't it work? Under what circumstances (if any) will it? [Troy said he no longer has the problem with the current madwifi drivers, thinks it was a problem with the old wds-branch code].
Access points
Location |
Part of roof |
Hardware |
Interface/IP address |
Int/Channel |
Antenna |
NAYA |
SW corner |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.2 |
wifi0/165(wds to commons) |
17 dBi to Commons |
wifi1/1 |
9 dbi 120deg pointing S |
||||
NW corner |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.3 |
wifi0/165(wds to ed) |
17 dBi to Ed's |
|
wifi1/11 |
9 dbi 120deg pointing NW |
||||
SE corner |
Cisco |
BVI1(Dot11Radio0,FastEth0)/10.11.104.4 |
Dot11Radio0/11 |
9 dbi 120deg pointing E |
|
Commons |
SE corner |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.5 |
wifi0/165(wds to naya-sw,west) |
8 dBi 802.11a omni |
wifi1/1 |
7 dBi omni (w/down-tilt) |
||||
Dog shop |
Edimax |
??/10.11.104.15 |
??/?? |
integrated omni |
|
Cecily's |
Chimney |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.8 |
wifi0/165(wds to commons) |
17 dBi to Commons |
wifi1/1 |
9 dBi omni |
||||
Ed's |
Chimney |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.9 |
wifi1/165(wds to naya-nw) |
17 dBi to NAYA NW |
wifi0/1 |
9 dBi omni |
See ChannelFrequencyChart for reasoning about channels, and channel choices.
MAC addresses
mississippi |
Interface |
MAC |
64.105.215.242 |
eth0 |
00:00:F8:06:C0:37 |
10.11.104.1 |
eth1 |
00:10:5A:04:1E:09 |
metrix-naya-sw |
Interface |
MAC |
10.11.104.2 |
wifi0 |
00:02:6F:21:EC:AA |
wifi1 |
00:02:6F:21:EC:A5 |
|
eth0(br0) |
00:00:24:C3:A9:C0 |
|
metrix-naya-nw |
Interface |
MAC |
10.11.104.3 |
wifi0 |
00:02:6F:21:EC:A8 |
wifi1 |
00:02:6F:21:EC:A6 |
|
eth0(br0) |
00:00:24:C3:A9:B4 |
|
metrix-commons |
Interface |
MAC |
10.11.104.5 |
wifi0 |
00:02:6F:21:EC:A9 |
wifi1 |
00:02:6F:21:E9:49 |
|
eth0(br0) |
00:00:24:C3:A9:A0 |
|
cisco-commons |
Interface |
MAC |
10.11.104.6 |
bridge |
00:0F:34:DF:9A:DD |
metrix-west |
Interface |
MAC |
10.11.104.8 |
wifi0 |
00:02:6F:21:EF:ED |
wifi1 |
00:02:6F:21:EF:F2 |
|
eth0(br0) |
00:00:24:c3:a9:ac |
|
metrix-ed |
Interface |
MAC |
10.11.104.9 |
wifi0 |
00:02:6F:21:EF:F0 |
wifi1 |
00:02:6F:21:EF:F1 |
|
eth0(br0) |
00:00:24:C3:E4:1C |
|
metrix-troy (not deployed) |
Interface |
MAC |
10.11.104.x |
eth0 |
00:00:24:C3:E4:30 |
metrix-russell (not deployed) |
Interface |
MAC |
10.11.104.y |
ath0 |
00:02:6F:21:EC:A2 |
ath1 |
00:02:6F:21:EC:A1 |
|
eth0(br0) |
00:00:24:C3:A9:B8 |
|
metrix-dje (not deployed) |
Interface |
MAC |
10.11.104.z |
ath0 |
00:02:6f:20:f7:2b |
ath1 |
00:02:6f:21:e8:2b |
|
eth0(br0) |
00:00:24:c2:39:d0 |
|
edimax-commons |
Interface |
MAC |
10.11.104.15 |
bridge |
00:0E:2E:3C:4B:7D |
edimax-freshpot |
Interface |
MAC |
10.11.104.16 |
bridge |
00:0E:2E:3C:4B:88 |
RussellSenior currently has both metrix-russell and metrix-dje setup in a test rig. Metrix-dje uses a Soekris 4526 board with 486 processor, different than the standard Metrix Mark II we are using on the project, which use a Soekris 4826 board with a Geode (pentium-like) processor. TroyJaqua has metrix-troy.
Note: When removing cisco-commons, we clipped off the ethernet and wrapped the severed end in tacky-tape. The cisco-specific PoE wiring was accomodated using an adapter section inside the enclosure. The severed tip was wired (I think) normally:
- white-orange
- orange
- white-green
- blue
- white-blue
- green
- white-brown
- brown
When opening the enclosure, there was a notable scent of cooking electronics. Not overpowering, but I noticed it. --RussellSenior
See MississippiMetrixConfiguration for a method of preparing and updating the software on the metrixes.