1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

My client bridge setup

Discussion in 'DD-WRT Firmware' started by tallnycguy, Feb 4, 2006.

  1. tallnycguy

    tallnycguy Network Guru Member

    Hello all, I'm new to this site. I want to let you all know that I got my client bridge setup using the information given on this forum by searching various posts. It took me about 3 days but I finally got it working fairly well. I want to give thanks to all those who contributed to this forum cuz without the knowledge it would probably have taken me a lot longer.

    Let me start out by saying that my setup includes a WRT54Gv3.0 as the MAIN router and a WRT54GSv1.0 as the CLIENT router.

    I got this setup working in client-bridged mode with WPA/AES. It was my initial hope that I wouldn't have to change any settings on my MAIN router and just be able to connect the CLIENT router as a regular client. This was not possible because prior to beginning this project I had WPA2/AES running. Whenever I try to run client-bridge using WPA2 AES or TKIP the CLIENT never can really establish a solid association with MAIN. On the MAIN status->wireless page the Clients section shows the MAC of the CLIENT coming in and out whenever I hit refresh and the signal is always 0 and SNR is -100. If I change my encryption to WPA/AES then I get a solid association between MAIN and CLIENT with signal -58 and SNR 42. Any ideas on why WPA2 doesn't seem to work?

    Another interesting thing I noticed is that when the only device that connects to the MAIN router is the CLIENT router over wireless then throughput is pretty low somewhere around 3 Mbps but as soon as I fire up my laptop and get it to join the wireless network on MAIN then throughput across the bridge suddenly goes up to like 18 Mbps even though the laptop is just sitting there connected but not really passing any traffic. Throughput testing was being done using 2 wired desktops one each connected to a LAN port on each router. Again any ideas why this is??? Weird!!!

    Another problem I ran into was initially I had to set the MAIN router to mixed mode instead of G-only otherwise CLIENT wouldn't connect regardless of encryption type or even no encryption. But somehow later on this was no longer a problem and now I have both ends set to G-only.

    Anyhow this is the little project I undertook, again thanks all for your help. I can now return an expensive WMP54GX PCI card I had bought for my desktop for about $120 and instead use the onboard 10/100 ethernet connected to my CLIENT bridge router as well as have an addtional 4 more LAN ports. How awesome is that!!!
  2. electrickery

    electrickery Network Guru Member

    Using DD-WRT v23 mini (11/01/05), I succeeded with Client bridge mode with WPA changing only the following from the defaults:

    Setup > Basic Setup
     DHCP Server:  Disable
    Wireless > Basic Settings
     Wireless Mode:               Client Bridged
     Wireless Network Mode:  Mixed
    Wireless > Wireless Security
     Security Mode:    WPA Pre-Shared Key
     WPA Algorithms:  TKIP
     WPA Shared Key:  <equal to other side>
    Status > Wireless
     Survey  # (shows list of available networks. Select one, then click Join en Close.)
    The other side is a standard Hyper-WRT 2.0. When connected, both the DD-WRT router and all connected computers appear in the DHCP Active IP Table.

    Post edit: This is tested with DD-WRT v23 (12/25/05) (mini/generic) too.
  3. tallnycguy

    tallnycguy Network Guru Member

    I got WPA working with client bridged setup but not WPA2 but then I found out information from another forum that WPA2 won't work in client bridge because the code for that is not available, it is closed source binary. However in client routed mode WPA2 AES-CCMP works great on my WRT54Gv3. I tried setting up WPA2 on my WRT54GSv1.0 in client routed but it wouldn't work. Don't know why, probably something hardware specific.

Share This Page