|
← Revision 90 as of 2006-01-13 02:49:31
Size: 7105
Comment: Add my diagram
|
← Revision 91 as of 2006-01-14 23:11:02 →
Size: 7259
Comment: Add chevy to hardware list
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 33: | Line 33: |
| ||<|9>NAYA ||<|2>Laundry Room||<|2>naya ||10.11.104.1 ||eth1 ||{{{00:10:5A:04:1E:09}}}||<-4>N/A|| | ||<|9>NAYA ||<|3>Laundry Room||<|2>naya ||10.11.104.1 ||eth1 ||{{{00:10:5A:04:1E:09}}}||<-4>N/A|| |
| Line 35: | Line 35: |
| || chevy ||10.11.104.7 ||eth0 ||{{{00:C0:4F:05:92:84}}}||<-3>N/A||External 64.105.215.243 forward|| |
Mississippi Network Diagram and Configuration
[http://www.personaltelco.net/~caleb/diagrams/MississippiNetworkDiagram.jpg]
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
MississippiLoadBalancing: We use both the NAYA DSL line, and the NodeFreshPot line.
The above diagram was made with Dia, and it's .dia file is [http://www.personaltelco.net/~caleb/diagrams/ here], please feel free to improve it.
Another [http://www.personaltelco.net/~brj/dia/wifimiss.dia diagram]:
[http://www.personaltelco.net/~brj/dia/wifimiss.png]
Include(MississippiNetworkNews, "NEWS", 2, from="^.*$")
TODO
Add StephouseNetworks Logo to Buick's NoCatAuth 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...
- 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].
Hardware
Building |
Location |
Hostname |
IP address |
Interface |
MAC |
Radio |
Chan |
To |
Notes |
NAYA |
Laundry Room |
naya |
10.11.104.1 |
eth1 |
00:10:5A:04:1E:09 |
N/A |
|||
64.105.215.242 |
eth0 |
00:00:F8:06:C0:37 |
N/A |
||||||
chevy |
10.11.104.7 |
eth0 |
00:C0:4F:05:92:84 |
N/A |
External 64.105.215.243 forward |
||||
SW corner |
metrix-naya-sw |
br0/10.11.104.2 |
eth0 |
00:00:24:C3:A9:C0 |
N/A |
||||
ath2 |
00:02:6F:21:EC:AA |
wifi0 |
165 |
commons-ath2 |
17 dBi to Commons |
||||
ath0 |
00:02:6F:21:EC:A5 |
wifi1 |
1 |
clients |
9 dbi 120deg pointing S |
||||
NW corner |
metrix-naya-nw |
br0/10.11.104.3 |
eth0 |
00:00:24:C3:A9:B4 |
N/A |
||||
ath2 |
00:02:6F:21:EC:A8 |
wifi0 |
165 |
ed-ath3 |
17 dBi to Ed's |
||||
ath0 |
00:02:6F:21:EC:A6 |
wifi1 |
11 |
clients |
9 dbi 120deg pointing NW |
||||
SE corner |
cisco-naya-se |
10.11.104.4 |
BVI1 |
|
Dot11Radio0 |
11 |
clients |
9 dbi 120deg pointing E |
|
Back room |
liberace |
10.11.104.20 |
eth2 |
00:20:78:03:ed:66 |
N/A |
||||
10.11.7.193 |
br0/eth1 |
00:00:f8:07:63:f5 |
N/A |
||||||
192.168.1.254 |
eth0 |
00:10:5a:a6:06:98 |
N/A |
NATed to 67.101.8.16 |
|||||
Indoors(ledge behind counter) |
edimax-freshpot |
bridge/10.11.104.16 |
br |
00:0E:2E:3C:4B:88 |
|
11 |
naya-nw-ath0(client) |
integrated omni |
|
Commons |
SE corner |
metrix-commons |
br0/10.11.104.5 |
eth0 |
00:00:24:C3:A9:A0 |
N/A |
|||
ath2 |
00:02:6F:21:EC:A8 |
wifi0 |
165 |
naya-sw-ath2 |
8 dBi 802.11a omni |
||||
ath3 |
west-ath2 |
||||||||
ath0 |
00:02:6F:21:E9:49 |
wifi1 |
1 |
clients |
7 dBi omni (w/down-tilt) |
||||
Dog shop |
edimax-commons |
bridge/10.11.104.15 |
br |
00:0E:2E:3C:4B:7D |
|
1 |
clients |
integrated omni |
|
Cecily's |
Chimney |
metrix-west |
br0/10.11.104.8 |
eth0 |
00:00:24:c3:a9:ac |
N/A |
|||
ath2 |
00:02:6F:21:EF:ED |
wifi0 |
165 |
commons-ath3 |
17 dBi to Commons |
||||
ath0 |
00:02:6F:21:EF:F2 |
wifi1 |
1 |
clients |
9 dBi omni |
||||
Ed's |
Chimney |
metrix-ed |
br0/10.11.104.9 |
eth0 |
00:00:24:C3:E4:1C |
N/A |
|||
ath3 |
00:02:6F:21:EF:F1 |
wifi1 |
165 |
naya-nw-ath2 |
17 dBi to NAYA NW |
||||
ath0 |
00:02:6F:21:EF:F0 |
wifi0 |
1 |
clients |
9 dBi omni |
||||
See ChannelFrequencyChart for reasoning about channels, and channel choices.
Other hardware
cisco-commons (not deployed) |
Interface |
MAC |
10.11.104.6 |
bridge |
00:0F:34:DF:9A:DD |
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 |
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 cisco-commons enclosure, there was a notable scent of cooking electronics. Not overpowering, but enough so I noticed it. --RussellSenior
See MississippiMetrixConfiguration for a method of preparing and updating the software on the metrixes.