Sunday, February 03, 2008

So, after asking around about my new internet situation, i was informed that there was no way for me to set it up as i wanted to. I had to have my WRT54G as the slave and the new neatgear WGR614 as my master device. With that in mind, i reattached the netgear to my new NTL broadband and put the WRT54G back to it's old position beside the two wired computers.

Just in case anyone else needs to do something like this, this is how you create a wireless bridge between two routers:


Equipment needed:
1) A router which supports the 'Client' mode. In my case, a linksys WRT54G with the openwrt firmware, the 'slave' router.
2) Any other wireless router, the 'master' router.


Setup:

Master Router
1) Connect it to your internet box (be it an ADSL modem or whatever).
2) Set up the wireless connection as per normal.
3) Enable uPnP and DHCP as required.

This router will accept all wireless connections, and can also accept wired connections via it's LAN ports as per usual. All port forwarding should be done via this router.

Slave router
1) Connect any wired computers to LAN ports on the router. Make sure nothing is connected to the WAN port. You won't be using this.
2) Set the wireless to use the same SSID (network name) and frequency as the master router.
3) Set the wireless connection to use 'Client' mode. In the case of openwrt, the correct mode is called 'Client (bridged)'. In this mode, the router will look for the wireless network with the SSID you specified and connect to it like a regular laptop.
4) Disable uPnP and DHCP on this router.

Note: The slave router cannot accept wireless connections anymore. It can only forward wired computers to your master router.

With that done, my two desktops remain in the same old room as always and connect wirelessly to my master router, thus giving them access to the net and having them accessible to the wireless clients.

The only problem is that the new router is a bit limited in it's configuration and so will end up being replaced in the near future. For the moment, it does the job fine.

1 comment:

Bryan said...

I have a similar setup. I have cable coming in our front room, and DSL in my bedroom. I also have an attic where I like to keep my dev boxes and vm hosts (backend network). They are noisy, and need cool air flow.

I use the same client setup between the AP in the front room and the attic.

For the DSL line in my bedroom, I have WDS (basically a transparent wireless bridge) between two more APs - again between the bedroom and the attic. This way I can have boxes in the attic with static IPs off the DSL line.

In the attic on the backend network, I have a few tagged and untagged vlan ports on a cisco switch that route on the network behind the DMZ of the DSL line to the comcast line.

All of the wireless is done with DD-WRT: http://www.dd-wrt.com/wiki/index.php/Wireless_Bridge
and
http://www.dd-wrt.com/wiki/index.php/WDS

Enjoy!

Hit Counter