How to Convert a Second Router into a Wireless Bridge

November 7, 2011 at 5:29 am by

23,298 Total Views
clientbridge
If you are planning to expand your wireless home network and want it all wire-free and no cabling cluttering up your home, you may be able to turn a second wireless router into a Bridge; even an old router would do by using a DD-WRT free firmware.
Do not attempt to make a Client Bridge with DD-WRT SP1 as it will not work.Please see the following link for Supported Routers: http://www.dd-wrt.com/wiki/index.php/Supported_Devices
If your router is not supported please do not install DD-WRT as it could render your router unusable.
Download DD-WRT here: Router Database | www.dd-wrt.com. Make sure to download the .bin file.In this Tutorial, we will use a Linksys Router; the router setting will be different than for other Routers (D-Link, Netgear, Belkin, etc) but with some similarities. On the Wireless Access Point (WAP) please reserve an IP Address for the second router to avoid IP Address conflicts; I suggest 192.168.1.2. This is done by entering the IP address of the router into the address bar of a web browser 192.168.1.1.1. To begin, turn off all these devices, start with the WAP, second router to be converted as Wireless Bridge and computer.2. Connect a computer to the second router by using a patch network cable. Make sure that the network cable is plugged into one of the LAN ports (usually 4 ports).

3. Power up the second router and wait for the lights to stabilize then power up the computer.

4. Follow the guide in your router’s manual to log into the router’s configuration. Make sure that you know the User Name and Password of the router. This is done by entering the IP address of the router into the address bar of a web browser. For example, the Linksys Router’s IP is http://192.168.1.1.

5. Reset the second router by using a paperclip and insert it into the small hole in the back of the router for about 10 to 20 seconds. Wait until all lights light up to indicate that the router has reset. This clears any settings and restores it to the factory default setting.

6. Install DD-WRT onto the second router by following the guide: Installation – DD-WRT Wiki
Note: Be cautious on installing the DD-WRT as you might “brick” the router. Please make sure that you read the Installation instructions very carefully.

7. Go to the firmware update page and upload the firmware.

8. Navigate to the second router’s IP Address using your browser if not automatically directed after the firmware upgrade.

9. Setup a username and password for access to the DD-WRT Control Panel before you log in and then try to log on again.

10. Locate the Wireless Tab and change the Wireless Mode to Client Bridge. Set the SSID to match the SSID of your WAP and click Save.

11. On the Wireless Security tab, match the security settings (WEP/WAP/WPA2) of your WAP router, then click Save.

12. Find the page to setup the Static IP and ensure that the DHCP server is set to Disabled.

Router IP: 192.168.1.2
Subnet Mask: 255.255.255.0
Gateway: 192.168.1.2
Static DNS 1: 192.168.1.1
Click Save.

13. On the Security tab check that the Firewall is set to disabled.

14. Under Setup check that the WAN interface is set to disabled.

15. Under Advanced routing or administration, check that routing is enabled.

16. Power up the WAP and wait for the lights to stabilize.

17. You may now click apply on all of the new settings that have been modified then reboot the router for the changes to take effect. This second router can now act as a Wireless Bridge on your network.

18. Navigate to the WAP’s Router IP Address via a browser and under status go to connected clients. Your second router Mac Address should be displayed here and authorized should be read as Yes.

19. Navigate to the second router (DD-WRT) through an IP Address via a browser but read and setup the connection first using Important Notes at the bottom of this page and go to the status page and then go to the Wireless tab. Scroll down to access points and your WAP router should be listed there.

How to Connect your Computer to the Wireless Bridge:

In Windows XP -Click on Start>Control Panel>Network Connections
In Windows 7 or Vista – Click on Start>Control Panel>Network and Sharing Centre>Change adapter settings
Right click Wireless Network Connection and select properties. Enter the admin credentials if prompted. Scroll down to Internet Protocol Version 4 (TCPIPv4), go into Advanced and under Default Gateway add 192.168.1.2 click OK and OK again.

On the computers using the Wireless Bridge open a command prompt:
Click on Start, in run (XP) or search box (7/Vista) type cmd, press enter.
Type ipconfig /release and press Enter, then type ipconfig /renew and press Enter.
Now, type ipconfig /all and press Enter and you should now see the second routers IP as the first default gateway then your WAP as the second gateway.
You will see an unidentified network with internet access when you hover over the wireless icon in the taskbar; this is the Wireless Bridge between the two routers and will be listed as a public network in Network and sharing centre.

Please remember: This is for Wireless Internet Connectivity only.

Important notes: If you wish to connect to the DD-WRT Control Panel on the second router you will need to connect a patch network cable to one of the LAN Ports on the second router and the other end to one of your computers and navigate as follows:

In Windows XP – Click on Start>Control Panel>Network Connections.
In Windows 7 or Vista – Click on Start>Control Panel>Network and Sharing Centre>Change adapter settings.

Right click Local Area Connection and select properties. Enter credentials if prompted to do so and scroll down to Internet Protocol Version (TCPIPv4) then click the properties button. Manually assign the following information:
IP address: 192.168.1.50
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.1.2
DNS server addresses: 192.168.1.1
Click OK and OK again.

© 2011 The CyberMan and 2xg

__________________

Filed under Hardware, Networking, Software
Tagged .
  • Sublime5884

    OK,  it is a little clearer now. I have a feww computers and was having trouble with the “clutter” taht comes with having a network at home.

  • Sublime5884

    OK,  it is a little clearer now. I have a feww computers and was having trouble with the “clutter” taht comes with having a network at home.

  • LinCryst

    Awesome, thanks for the info, worked like a charm!  Definitely much better than the range extender that took hours and hours to get working correctly!  Wish I’d seen this before I bought it, but, now I have all the range I need for my network and it covers the entire house!  You rock!

  • Guest

    Just buy homeplugs

  • TheCyberMan

    Hi TheCyberMan here thanks for all your comments an easy and free solution for all not wishing  to shell out on extra equipment and go wireless.

    Hi guest did you follow the article  and you couldn’t get it too work. If you would like any assisatnce you can post in the link below:

    http://www.techsupportforum.com/forums/f31/
     

  • this-IT-guy

    Good Stuff

  • TheCyberMan

    Hi this-IT-guy thanks for your comment much appreciated who it has been usful to you and everyone else who has used the article.

  • Dhiraj Patra

    I have Ubuntu 12 PC with 2 Ethernet cards. ! (eth0) is connected with fiber broad band Internet connection and made as DHCP. Another (eth1) is make static IP like this ip:192.168.0.1, mask:255.255.255.0, gateway: 192.168.0.1, dns:208.67.222.222. 

    I have a laptop with Windows xp that ehternet with static ip:192.168.0.2, mask:192.168.0.1, mask:255.255.255.0, dns:208.67.222.222. and connected with ubuntu’s eht1 to share the internet.

    But I couldn’t even make ping 192.168.0.1 from client or 192.168.0.2 from ubnutu pc.

    But even after the added below code too not helped. Pl give me some suggestion.

    I have added some command also from:

    Ubuntu Internet Gateway Method (iptables)

    You will
    need two network cards in the gateway computer, or a PPP interface and a
    network card. One network card (or PPP interface) connects to the
    Internet. We will call this card eth0. The other card connects to your internal network. We will call this eth1. It is also possible to do ICS with a single network card. In this case, use eth0 for the Internet and eth0:0 for the internal network.
    Internet <> eth0 Ubuntu gateway eth1 <> Client PC Internet <> ppp0 Ubuntu gateway eth1 <> Client PC Internet <> eth0 Ubuntu gateway eth0:0 <> Client PC

    Gateway set up

    The
    following example will focus on the most common gateway setup: an Ubuntu
    computer with two wired network adapters (eth0 and eth1) hosting ICS to
    a static internal network configured for the 192.168.0.x subnet.
    For
    this example, eth0 is used to represent the network card connected to
    the Internet, and eth1 represents the network card connected to a client
    PC. You can replace eth0 and eth1 as needed for your situation. Also,
    any private IP subnet can be used for the internal network IP addresses.
    In summary:
    eth0 = the network adapter with internet (external or WAN).
    eth1 = the network adapter to which a second computer is attached (internal or LAN).
    192.168.0.x = IP subnet for eth1

    Your setup may be different. If so, make sure to change them accordingly in the following commands.

    Configure internal network card

    Configure your internal network card (eth1) for static IP like so:
    sudo ip addr add 192.168.0.1/24 dev eth0
    The external and internal network cards cannot be on the same subnet.

    Configure NAT

    Configure iptables for NAT translation so that packets can be correctly routed through the Ubuntu gateway.
    sudo iptables -A FORWARD -o eth0 -i eth1 -s 192.168.0.0/24 -m conntrack –ctstate NEW -j ACCEPT
    sudo iptables -A FORWARD -m conntrack –ctstate ESTABLISHED,RELATED -j ACCEPT
    sudo iptables -A POSTROUTING -t nat -j MASQUERADE
    The first rule allows forwarded packets (initial ones). The second rule allows forwarding of established connection packets (and those related to ones that started). The third rule does the NAT.
    IPtables settings need to be set-up at each boot (they are not saved automatically), with the following commands:
    Save the iptables:

    sudo iptables-save | sudo tee /etc/iptables.sav
    Edit /etc/rc.local and add the following lines before the “exit 0″ line:

    iptables-restore /proc/sys/net/ipv4/ip_forward”

    Edit /etc/sysctl.conf, and (up to 10.04) add these lines:

    net.ipv4.conf.default.forwarding=1
    net.ipv4.conf.all.forwarding=1
    The /etc/sysctl.conf edit is required because of the following bug in Hardy and later releases: Launchpad Bug Report
    From 10.10 onwards, it suffices to edit /etc/sysctl.conf and uncomment:

    #net.ipv4.ip_forward=1
    … so that it reads:
    net.ipv4.ip_forward=1