i had to go back to 14896 to get a working AP/client bridge configured between whr-g300n & whr-hp-g300n, similar to your NetDesired.jpg image
i had tried a 15xxx and a 16xxx builds before i went back to 14896 that worked. i only get about 1-3 days uptime because of too many neighbors...
i have the client bridge watchdog the AP (WDS/Connection Watchdog) set for 30 minutes... _________________ 2x WRT54G v5, 2x WRT54G v2
1x WRT54G2 v1
2x BUFFALO WHR-G54S
2x BUFFALO WHR-G300N v2
1x BUFFLOW WHR-HP-G300N
1x La Fonera
FON Client Bridge tutorial
Posted: Tue May 10, 2011 20:15 Post subject: TP-Link TL-WR740N V2 frustration solution partially
After spending many hours trying to configure my TP-Link TL-WR740N V2 as a repeater, searching a lot on the dd-wrt forum and elsewhere, reading that other users have the same problem and feeling very frustrated I have arrived at a solution with which I can live, although the result is not a real repeater solution. Maybe other frustrated users are interested in the story.
At first how I did not succeed:
The first instructions I tried to follow were at
I installed the Build 15778 from
for the TP-Link WR740N V2 and then tried to follow the instructions at
There is a chapter there on routers using the Atheros chipset. Trying to follow these instructions I could get a configuration which made a connection between laptop WLAN and the ath0.1 interface but I never could get a connection to the internet.
I then read the posting of penko_bg at
who briefly explained
>„first i connect like client with dhcp setings,then i make my router with different ip,and start dhcp >server,and final i add second network with different name(you can try to add second network with >same name, like client name network)“
and got the impression that all the time I had tried something which ist not possible
Then I found instructions at
>DO NOT USE THE RECOMMENDED BUILDS ON THE DD-WRT HOMEPAGE, those >are outdated and buggy.
>There is no "Repeater" mode on Atheros units, but you still can use it as repeater, just set the >original interface as "client" and get it to connect to your AP, then create a virtual interface to >broadcast the new SSID.
This explained why trying to configure a client-bridge was not successful.
Important from the instructions
>Also note that the device should be in GATEWAY MODE instead of ROUTER mode, otherwise >Masquerade/NAT does not happen.
So I ended up as follows:
On device A: Thomson ADSL-Gateway
WLAN-Access Point -1 ( DHCP server on) in subnet 10.0.0.X., SSID A
On device B: TP-Link TL-WR740N V2
Ath0 WLAN interface configured as CLIENT with same SSID Aconnected to WLAN-Access Point -1 receiving network configuration by DHCP server there, is also in subnet 10.0.0.X.
Ath0.1 WLAN-interface configured as AP with new SSID B. Subnet 192.168.1.X and DHCP-server on.
Means the WR740N works as a router connections wirelessly on the WAN-side:
WAN connection: WLAN-ath0
LAN-connection: WLAN ath.01 and the 4 or 5 LAN connectors.
I first tried out without any security, worked out. The same way it worked with WPA2 etc on both subnets.
The only drawback ist that the subnets are different and so at the moment I cannot access my network printer in subnet 10.0.0.X from PCs in subnet 192.168.1.X. But the main aim, to get a wireless internet connection to the end of my garden, is fulfilled. If one tries to get access on the two subnets it might be useful to define them as 10.0.0.X and 10.0.1.X and subnet masks permitting access between the subnets.
BTW I contacted TP-Link about differences between WR740N and WR740ND. They answered that there really is no difference except the detachable antenna. Why are there different firmwares for the two models?
I am still curious, whether anybody has succeeded to get a configuration with the secondary net having the same subnet and SSID? I have stored my configs to be able to get back to a working solution and will try to get a solution with the same subnet again, maybe it is still possible?
The TG585 V7 Firmware 220.127.116.11 does not support WDS on its webinterface but I read that it supports WDS via CLI. At the moment I am not ready to dive into the CLI manual and try it out. Do I remember correctly that WDS supports only WEP and not WPA?
My AP is a Netgear WGR614v9 (no DD-WRT available ) set up with WPA-PSK2 TKIP+AES with DHCP and UPnP.
Did the steps mentioned above, but I could not for the life of me figure out what I was doing wrong!
Turns out the radio was off, which I knew bu couldn't figure out how to turn it on. To turn it on, go to the basic setting page, and the first selection drop-down menu, either change it to DHCP and APPLY Settings, or manually configure the IP settings.
Posted: Thu Jul 07, 2011 23:18 Post subject: POSSIBLE SOLUTION
I just spent an entire day struggling with client bridge problems on an WZR-HP-G300NH. I was eventually able to get everything running stably and with good performance by going all the way back to build 14289.
I have not tried 14896 yet. I will try it soon and let you know if it works for me too.
Hello friend, I have the same problem. I installed that will build you stated, but which procedure should I set it. I have tried several ways without being able to get it. I appreciate your help me please.