Have a building at the other end of your property not served by cable/phone? Need to cross another’s property to get internet access to your remote building, a WiFi wireless bridge might be the answer.
I work part-time at a radio station on Cape Cod and they needed to add internet connectivity to their transmitter site. This site is about 550 feet distant, across a road and several other properties so a direct run of Cat-5 or 6 was impossible. Also we did not want the added expense of a second ISP subscription so enter high power routers and the dd-wrt open source software.
View larger map
It was decided early on to use panel antennas and high power routers compatible with the dd-wrt software suite. The Luxul X-Wav Surefire flat panel antennas were already purchased by the station owners, but proved to be pretty good. The router, as recommended by the dd-wrt organization were Buffalo WHR-HP-G54′s. They have one detachable antenna, a built in antenna and are switchable, so that all the available power and receive sensitivity can be directed to either or both.

Luxul Panel Antenna at Transmitter
After installation of the dd-wrt software, configuration of the routers was problematic, but not for lack of capability, but rather hard to read documentation at the dd-wrt wiki. This entry is intended to alleviate some of that difficulty.
First and foremost, get as much of the network working on the bench, across the room, then across the yard, before deploying the equipment in the field. This simple action will save you alot of trips when you inevitably lose control over either end and have to visit it personally.
The originating, local end is referred to as the “Primary Router”, the remote location, the “Remote Router” or “Bridge Router”. In our particular configration the Primary Router is not the master network router, but is simply used on the network as a workgroup switch locally and as one end of the WiFi path. As a result, many features are turned off.
After installing the dd-wrt software, there is not much configuration on the Primary router and will vary depending on your installation. You must have the wireless security set to be WEP or WPA-aes (WPA2-Personal works as well). In my case I had shut off the internal (left) antenna directing everything to the outside (right) panel and had shut off DHCP as the Primary router would be handling that. Finally, I set the IP to 192.160.0.50, something outside the DHCP range but easily remembered.
On the Secondary router, perform the following steps.
- Perform a “30-30-30″ reset on the router. Hold the reset button for 30 seconds, keep holding the reset button and power down the router for 30 seconds, and while continuing to hold the reset button, power up the router and continue holding it for another 30 seconds. A watch or stopwatch will be helpful.
- Connect a cable from your computer to one of the LAN ports on your router (one of the group of 4).
- Configure your computer to have a static IP address in the same subnet (192.168.1.9 in my case).
- Point your browser at 192.168.1.1 and open the dd-wrt webgui.
- You should be asked to change your password and username. Carefully type these in. If you aren’t asked for a password and username, do a hard reset, this time doing it properly! Hit change password.
- Go FIRST to the wireless tab, wireless security and enter the security type and key that matches your primary router. You must use WEP or WPA2-aes to have dd-wrt work reliably. In my case, WPA2-Personal worked fine with a simple passphrase. Hit SAVE then APPLY Settings.
NOTE: You may wish to do the rest of this setup with wireless security disabled. Then enable it as your last act. This will require access to both sides.
- Go to the Wireless/Basic Settings page and change the wireless mode to Client Bridge.
- Your wireless network mode, channel and encryption should be set to the same as the primary router.
- If you are using N only or Mixed with N, set your wireless channel width to match your primary.
- Set the wireless network name to exactly the same as your primary router. Make sure spelling and capitalization match.
- Hit SAVE at the bottom. Then hit APPLY.
- Check to make sure all the configurations, including the mode, saved and the mode is still client bridge. If any changed, fix them, and save again.
- Goto Setup/Basic Setup and enter a router local IP address of something not already occupied on your network and easy to remember (I chose 192.168.0.254 The client bridge must match the subnet of the primary router) Leave subnet mask at 255.255.255.0.
- Set the Gateway IP to your primary router. (192.168.0.50 in my case)
- Leave Local DNS blank.
- Check Assign Wan port to a switch, if you wish to. (this will give you one more LAN port)
- Change your timezone and DST to match where you are.
- Hit SAVE at the bottom. Then hit APPLY.
- Set your browser to the router’s new IP (192.168.0.254 in my case) and login to your router. You may need to restart your browser.
- Goto Security, Firewall. Under Block Wan Requests, uncheck everything but “Filter Multicast” (Leave Filter multicast checked).
- Hit SAVE at the bottom. Then hit APPLY.
- Disable SPI Firewall (I also disabled the firewall on the primary router as it is not directly connected to the internet, I let the main router handle this function).
- Hit SAVE at the bottom, then hit APPLY.
- Go to setup/advanced routing and change the operating mode from “gateway” to router.
- Hit SAVE at the bottom, then hit APPLY.
- In my case, I routed the receive and transmit antennas to the outdoor panels (‘right’ antenna is the connecterized external antenna). To to Wireless/Advanced and set TX Antenna to Right and RX Antenna to Right. Also at this time, I increased my TX power to 175, too high and the amplifier will eventually die.
- Hit SAVE at the bottom, then hit APPLY.
- Go to Status/Wireless and hit Site Survey, and Join the appropriate wireless network. The access point table should show the MAC address of your primary router, along with signal strength. (SSID Broadcast MUST be enabled on your primary router). Note: you cannot do this from the Primary side, your bridge is not visible, its not an AP. All we get is a nice list of the neighbors. The Secondary router, or the bridge, has no other neighbors.
- You should now be able to ping various machines on either side of the bridge.
- After some time, you should have nice healthy packet numbers at Status/Wireless. A few bad packets are normal, I currently have 159815 good / 0 bad receive, and 440968 good /71 bad transmit on the Primary router and 118674 good / 0 bad receive and 63801 good / 26 bad transmit on the Secondary router (different uptimes).
- If everything is working as expected, as a final act, on the Primary side of the bridge, log into the Secondary router (192.168.0.254 in my case), go to Administration/Backup and hit BACKUP. Rename this file to something memorable. Do the same (or similar if not dd-wrt) on the Primary router (192.168.0.50 in my case).
It should be noted, I have experienced some minor packet loss (missed pings) and some served pages timing out (the remote end has equipment with small webservers integrated). I believe this is due to the Windows ARP cache becoming confused. The wireless MAC address is not rewritable by the dd-wrt firmware, so each IP address at the Secondary end will have the same MAC address. I have not tested this with other OSs but I believe Mac and Linux will be more forgiving.
For further reading check out the dd-wrt Wiki