For: Crossville Housing Authority
Date of Completion: May 24, 2006
Project Goal: To provide internet access to computer in a remote part of a two building complex.
Narrative: When I was first approached to do this project I had just completed the Tansi Pro-shop, Maintenance, and Snack bar Wifi project. The Tansi project required aerial mounted antennas, poll boxes, and several Access Points. So when I first looked at the HAFH project I was thinking large scale. After playing around with the ideal of externally mounted antennas and 100′ coax runs I took a step back and decided to approach this from a more simplistic standpoint.
The facility had an existing 802.11b network worked by an old Linksys AP, which sat nearly under a counter/desk. The problem was that the signal from this older Linksys AP would not reach down into the lower building annex where the computer they wanted to network was located. Even with elevating the AP to the top of the desk we could not generate enough signal. The distance was about 250 feet, but transited 2 or 4 external walls of brick, and many internal walls of typical governmental construction. Signal could be had just inside of the closest wall of the annex building to the main building.
I decided to use a two AP approach to this problem, and create a small mesh network, using WDS. This would have the advantage of being able to easily install more computers in the annex building should the organization require it. It would also not require coax runs, and cat v runs from the nearest inner wall to the computer in which was in the rear of the annex.
I selected my new standard of the Linksys WRT54GL as the model of AP. I have recently moved to the WRT54GL from the WRT54G after ver 5 of the later made it impossible to install Linux based firmware. Of course the stock firmware on the WRT54GL does not support WDS, so I loaded both units up with openwrt, RC5, from www.openwrt.org.
Setup of the WDS did take some time. Of course the united need separate IP addresses, and the MAC address of each other in their respective wl_wds nvram values. It was strange, but the network did not come alive right at way. It seemed to take 5 to 7 minutes for the units to linkup, but once they did it worked flawlessly. The named the unit “Base” and “Remote” with IP address of 192.168.1.1 and 192.168.1.2 respectively. I also disable all firewalling and DHCP server services on “Remote” because those function are now handled by “Base”.
To maximize the signal I decided on elevated mounts for both AP. The “Base” unit also required two cat V cables going to it in addition to power. One line for the DSL connection, the other line for connection to a small 10/100 switch which would service some existing hard wired computers. I opted for the small switch in order to keep wires running up the wall to a minimum.

I have to say I was pleased with the mounting, the “Base” unit mounted nicely on a wall out of direct line of site from the door. The “Remote” unit I hid behind a banner is a on of the day care classrooms which was equidistant between “Base” and the computer we wanted to service. The only thing required to run to the “Remote” unit was power, which came from a convenient outlet just under the mounting point.

The last peace of the puzzle came from the system we wanted to service. I used a simple Linksys USB client card for wireless connectively, and to insure good single, it too was mounted on the wall.

I fired up all the APs and give them time to link up, then installed the USB client card. The target system found its network, attached, and pulled an IP address from DHCP on the first try. Because I had replaced the older Linksys 802.11b AP, I had to go around and link each of the existing computers to the new SSID. I used two ssid, HAFH1 (from the “Base” unit) and HAFH2 (from the “Remote” unit), I had read that it’s a good ideal to name them the same, but I felt this would create some confusion, given the close proximity of the units.
In the end all the systems gladly linked to the new ssid, and I discovered an added bonus, that because of building fade issues, some of the preexisting computer had greater signal strength to HAFH2 than that of HAFH1, so placing these other computer of HAFH2 only further validated the additional AP.


