Mississippi Network Diagram and Configuration
Buick 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.
Include(MississippiNetworkNews, "NEWS", 2, from="^.*$", to="^----$")
TODO
- Add connectable interfaces to eth0, ath0 and ath1 so that recovery from bridge failure is easier.
Followup on madwifi.org ticket [http://www.madwifi.org/ticket/166 166], which describes our problems with metrix-west.
- 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?
- Decommission (redundant) Cisco AP on Commons
- Ed's is mounted on the chimney, plugged in, talking to metrix-naya-nw. Need to try repointing antenna at Commons roof.
- Metrix-naya-sw currently does not have line-of-sight from Commons mast due to vegetation, but still a reasonable signal, probably want to use metrix-naya-nw for 11a backhaul instead for better line-of-sight, perhaps even replacing metrix-naya-sw with a single-radio device. Another option is to leave both metrixes pointing at Commons. The spanning-tree protocol (STP) should pick one to use and self-heal if one goes down.
- Metrix-naya-nw's ath0 is configured as a master for Ed's on ESSID backhaul-nw, channel 161. If we can get Ed's metrix connected to metrix-commons, then we should change metrix-naya-nw's ath0 into client on the 11a backhaul network and point its backfire antenna at metrix-commons.
- The Sector antennas on Naya might benefit from being repointed...
- Install link to second DSL line (in bookstore) and setup round-robin load balancing
- Need to install a "repeater" at Cecily's location, attached to the ethernet port on the PoE injector.
- Need to install a "repeater" at Amnesia brewing inside and behind the corrogated steel.
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 |
ath0/165/client |
17 dBi to Commons |
ath1/1 |
9 dbi 120deg pointing S |
||||
NW corner |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.3 |
ath0/161/master |
17 dBi to Ed's |
|
ath1/1 |
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 |
ath0/165/AP |
8 dBi 802.11a omni |
ath1/1 |
7 dBi omni (w/down-tilt) |
||||
Cisco |
BVI1(Dot11Radio0,FastEth0)/10.11.104.6 |
Dot11Radio0/11 |
9 dBi 120deg pointing SE |
||
Cecily's |
Chimney |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.8 |
ath0/165/client |
17 dBi to Commons |
ath1/1 |
9 dBi omni |
||||
Ed's |
Chimney |
Metrix |
br0(eth0,ath0,ath1)/10.11.104.9 |
ath1/161/client |
17 dBi to NAYA NW |
ath0/11 |
9 dBi omni |
See ChannelFrequencyChart for reasoning about channels, and channel choices.
MAC addresses
buick |
Interface |
MAC |
10.11.104.1 |
eth1 |
08:00:20:c5:9a:5c |
metrix-naya-sw |
Interface |
MAC |
10.11.104.2 |
ath0 |
00:02:6F:21:EC:AA |
ath1 |
00:02:6F:21:EC:A5 |
|
eth0(br0) |
00:00:24:C3:A9:C0 |
|
metrix-naya-nw |
Interface |
MAC |
10.11.104.3 |
ath0 |
00:02:6F:21:EC:A8 |
ath1 |
00:02:6F:21:EC:A6 |
|
eth0(br0) |
00:00:24:C3:A9:B4 |
|
metrix-commons |
Interface |
MAC |
10.11.104.5 |
ath0 |
00:02:6F:21:EC:A9 |
ath1 |
00:02:6F:21:E9:49 |
|
eth0(br0) |
00:00:24:C3:A9:A0 |
|
metrix-west |
Interface |
MAC |
10.11.104.8 |
ath0 |
00:02:6F:21:EF:ED |
ath1 |
00:02:6F:21:EF:F2 |
|
eth0(br0) |
00:00:24:c3:a9:ac |
|
metrix-ed |
Interface |
MAC |
10.11.104.9 |
ath0 |
00:02:6F:21:EF:F0 |
ath1 |
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 |
|
edimax-commons |
Interface |
MAC |
10.11.104.15 |
bridge |
00:0E:2E:3C:4B:7D |
Firmware Image
The image for the Metrix boxen is at http://cornerstone.personaltelco.net/~brj/metrix-missnet.img It is setup with all 3 interfaces bridged, and br0 set to 10.11.104.5/22.
To flash:
- Setup a sarge installer pxeboot environment.
Instructions at http://www.debian.org/releases/stable/i386/ch04s06.html.en
The pxelinux included with debian tries to use both the VGA emulation and the serial console. This causes problems. Use pxelinux.0 from http://centerclick.org/net4801/pxelinux/ instead.
- Use the serial console pxeboot config.
- Change all the 9600 to 19200 in the config.
- You probably want to add DEBIAN_FRONTEND=text to the boot options of the kernel you'll use. Use expert26.
- Netboot the metrix into the installer
- Attach a serial terminal.
- 19200 baud, 1 bit parity, no flow control
- Press ctrl+p at the prompt to get to the BIOS
boot f0
- Use expert26. You don't need any extra options.
- Go through the installer up through step 9 (Download installer components). This is where device drivers are loaded.
- After the drivers are loaded, go to a shell.
wget -O - http://somewhere/foo/metrix-missnet.img | dd of=/dev/discs/disc0/disc bs=1M (don't get it straight from cornerstone, copy it to your machine first)
- Reboot
Note: as of 2005-10-11 this process isn't working for me. The Metrix stalls during the PXELINUX stuff. I think it's probably just an issue with my setup but I've got it working fine using the documentation from Metrix. (- KeeganQuinn)
The way the Metrix website says to do it is actually better. When I was working on the metrixes, though, that documentation didn't exist, to my memory. The debian netboot was simply the easiest way I could find to get a shell netbooted. (- BenjaminJencks)
Can KeeganQuinn or BenjaminJencks please point at or reiterate the referred-to Metrix documentation here? --RussellSenior

