Posted: Thu Dec 30, 2010 23:41 Post subject: TP-LINK TL-WR740N 741ND 841N and client bridge problem
TL-WR740N, WR1043ND, WR741ND and WR841N
I download current version dd-wrt for each AP.
First, I decide to create WDS network. I read FAQ:
and all routers were configure successful. But after few hours on main router (WR1043ND) wi-fi go down. Only restart is helpful. The longest time that WDS network was working - 36h.
So after this I decide to configure routers in "client bridge" (repeater). I was try to connect WR740N, WR741ND and WR841N to main router WR1043ND as it is wrote at this page:
But it was impossible. In status - wireless - I was able to see connection to main router but network dos not working!
I spent 4 days with fighting with this problem and I discover that when I connect WR1043ND as a repeater bridge to WR740N or WR741ND or WR841N its working fine!
As you can read in my post I done all configuration as it wrote in wiki materials !!!
Client bridge doesn't work between the same version software (I tried official and the newest - 12/24/10) and the same router (for ex. between WR740N - I bought 2).
The same situation with WDS - all routers use the same dd-wrt software (I tried official and the newest).
I order now 2 new WR1043ND and I will try make WDS and client bridge network on 3 WR1043ND routers.
But I fell that something is wrong with software on WR740/741/841. Routers work fine as "standard" AP (I'm testing it in my work) but if You want try other mode than AP (client, client bridge, WDS) its not working at all or after some time, is stop working.
I read some post on other forums about 740/741/841 and people wrote that there is a problem with transfers and radio connection - most in N mode
I spend last 3 days searching materials and information about TP-LINK devices.
What I found:
1. openWRT doesn't support "client bridge" function
2. Gargoyle based on openWRT has got "client bridge" function (arp-nat) - but it's not efficient and network is slowing down.
3. WR740N v2 is the same as V1 (but I'm not sure in 100% - maybe tomorrow I will install openWRT on it)
So best what we can do at this moment is:
1. go back to "stock" firmware (do webrevert prepare by LOM: http://www.dd-wrt.com/phpBB2/viewtopic.php?t=85237) and use WDS function between TP-LINK atheros base routers (it's working fine - I tested it! - just for 1 day - I don't have enough time to test it - I going to do next week)
2. Install Gargoyle on 741/841/941/1043 and use "client bridge" - I'm going to test it when I receive new 741+941
3. Wait for support from DD-WRT ... ?(no body response for this problem yet !)
I just receive 1043, 941 and 741 and I installed openWRT Gargoyle and Client bridge is working fine between 1043 (main) - 941 and 741.
So I dropped buggy DDWRT to openwrt ...
My advice ... do the same ...
I'm looking for openWRT for WR740N or Gargoyle version.
On this site:
you can download Gargoyle test software for WR740N - it's should work but - I will test it tomorrow!
This software was prepared by one of member of www.eko.one.pl (Polish web page about openWRT and Gargoyle)
Hello i have 740nv rev2 and i use it like repeater for 1 day i think it work fine.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)
Posted: Sat Apr 30, 2011 3:29 Post subject: WR740N vs Client Bridge = Fail.
Just to add to the growing list of frustrated DDWRT'ers - spent several days with every conceivable combination / wiki instruction / random educated guesses to get the following to work, all failed, same as this thread is experiencing.
Internet to Cable Modem
to [A] wired Netgear RP614v3 (DHCP)
to [B] wired Netgear GS108 Gb switches
to [C] (primary) Dlink DIR655 AP (stock firmware)
.......(also tried a 2nd TPLINK WR740N as primary...fail)
to [E] (secondary) TPLINK WR740N (DDWRT)
to [F] wired laptop as test subject (wifi off) Eventually to be a Media Player if it ever works.
via - (including Gateway setting/Router setting/MAC filters to wireless/manual GW IP's/manual DNS IP's/30-30-30/rebooting 850 times.. etc etc)
. DDWRT V24 preSP2 15778 on the WR740N secondary
. Client Bridge - fail
. (at best connects to DIR655 as a client, but that's it.)
. Client - fail (no radio)
Perhaps I'm just an idiot because I couldn't get stock factory WDS firmware on two WR740N's to work either - they would associate, but that's it. No dhcp, no dns, no ping to anybody else whatsoever. Pretty much the same problem with DDWRT.
So now I have 4 routers and zero bridges.
Thanks for listening.
I attached pics of my "Before" - normal working network, and desired "After" - still desired. the link between C & E is the Client Bridge Conundrum.[/i]
Yes, I tried firmware and static ip's too I'm afraid. The two wr740n's would associate and sometimes (..sometimes) both would appear on the DHCP router as clients, but when the laptop was wired directly to the secondary on stock WDS..no dice! No ping, no dhcp (to laptop), nothing. Very odd - not how I thought it would work. I know it *must* work - two identical routers with a stock-offered WDS option..so it *must* be something else along the line in my setup (but of course that's OT for this group anyway). Either way, make no mistake - I'm still digging, but had to vent to the group to see if anyone had ideas I had not yet considered.
The Brainslayer ddwrt is one of those ideas (thank you for that) I will give it a try as well! Out with the family today, give me a day or two and I will report back.
|(to WAN port)
ROUTER x.x.0.1 (wired, DHCP, Netgear RP614v3)
|(from LAN port)
|===>wired to a bunch of other stuff too
|(to LAN port)
ROUTER x.x.0.101 (wireless, primary, Dlink DIR655)
ROUTER x.x.0.201 (wireless, secondary, ddwrt 16785, TPLINK WR740N)
[Set to Client Bridge = shows as client, Fail]
[Set to Client = radio off, Fail]
|(from/to LAN port)
Laptop x.x.0.211 (wired to LAN of secondary, WinVista)
"Fail" meaning: No connectivity - no PING, no DNS, no DHCP, no nothing. WebUI from laptop works to wired secondary, however. Neither PING nor IPCONFIG nor TRACERT could provide any evidence the routers even knew each other existed. The laptop would show as a client to the secondary, but with the forced alternate IP as shown - not via DHCP.
As an additional OT comment, I also tried stock-fimware WDS (maybe I'll try ddwrt WDS next...) and that also failed. They would associate, but same no-connectivity issues.
This is KooKooBananas.
Some seem to have on problem at all, and others have nothing BUT problems!