Client Bridge Mode on Atheros devices

Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware
Goto page Previous  1, 2, 3  Next

Client Bridge Mode working on Atheros with latest builds?
Yes
16%
 16%  [ 10 ]
No
71%
 71%  [ 43 ]
I have not tried it
11%
 11%  [ 7 ]
Total Votes : 60

Author Message
pigge
DD-WRT Novice


Joined: 07 Nov 2006
Posts: 36
Location: Stockholm

PostPosted: Wed Nov 03, 2010 18:42    Post subject: Reply with quote
hmmm, that's funny.. I'm writing this through the connection of my client bridge..
i have a WZR-HP-G300NH and i had the same FW and almost the same setup as RATMAN_rush,
except for the "Setup/basic"->Gateway (i had the ip of my 1st router here)
and "Wireless/Basic Settings"->Gateway but i tried the manual setting
under "Wireless/Basic Settings"->Gateway and set it to the ip of my 1st router,
and then rebooted.. and now it works.
It looks like the client bridge router doesn't get the default GW through dhcp then!?

now let's see for how long the connection between the two stays up
Sponsor
dejvid
DD-WRT User


Joined: 26 Sep 2010
Posts: 94

PostPosted: Wed Nov 03, 2010 22:51    Post subject: Reply with quote
I can confirm this issue. The GW address needs to be set under Wireless/Basic.
pigge wrote:
hmmm, that's funny.. I'm writing this through the connection of my client bridge..
i have a WZR-HP-G300NH and i had the same FW and almost the same setup as RATMAN_rush,
except for the "Setup/basic"->Gateway (i had the ip of my 1st router here)
and "Wireless/Basic Settings"->Gateway but i tried the manual setting
under "Wireless/Basic Settings"->Gateway and set it to the ip of my 1st router,
and then rebooted.. and now it works.
It looks like the client bridge router doesn't get the default GW through dhcp then!?

now let's see for how long the connection between the two stays up
RATMAN_rush
DD-WRT Novice


Joined: 01 Nov 2010
Posts: 5
Location: poland

PostPosted: Thu Nov 04, 2010 12:22    Post subject: Reply with quote
one more i put mac adress of 1router in Wireless/MAC Filter and i mark Permit only clients listed to access the wireless network
becouse after update frimware 2router can`t find 1router
devicemanager
DD-WRT Novice


Joined: 14 Aug 2010
Posts: 32

PostPosted: Fri Nov 05, 2010 1:04    Post subject: Reply with quote
pigge wrote:
hmmm, that's funny.. I'm writing this through the connection of my client bridge..
i have a WZR-HP-G300NH and i had the same FW and almost the same setup as RATMAN_rush,
except for the "Setup/basic"->Gateway (i had the ip of my 1st router here)
and "Wireless/Basic Settings"->Gateway but i tried the manual setting
under "Wireless/Basic Settings"->Gateway and set it to the ip of my 1st router,
and then rebooted.. and now it works.
It looks like the client bridge router doesn't get the default GW through dhcp then!?

now let's see for how long the connection between the two stays up


There is no mention of Gateway or an option for you to input an IP under "Wireless/Basic Settings"->Gateway

*** EDIT ***

I stand corrected. I just upgraded my client bridge back to 15506. I looked under wireless > basic settings and noticed a Default GW Mode so I set it to manual and input the static IP of router #1 (gateway). Internet traffic is now being passed and working! Thanks for the heads up folks.
MrDongles
DD-WRT Novice


Joined: 27 Oct 2010
Posts: 3

PostPosted: Tue Nov 09, 2010 13:56    Post subject: 15693 Reply with quote
I installed build 15693 a couple of days ago and the WZR bridge router no longer has the issue of dropping its connection.

I can come back two days later and turn on the PS3 and I am able to get an ip and connect to the network.
dejvid
DD-WRT User


Joined: 26 Sep 2010
Posts: 94

PostPosted: Wed Nov 10, 2010 10:02    Post subject: Reply with quote
Hello everybody,
I have just discovered something that looks quite interesting.

This is my network config:
1043ND AP 192.168.1.1
|
|
|
1043ND Client Bridge 192.168.1.2
|
|
|
wired PC 192.168.1.101

Now look what happens when I ping the units from the wired PC:

this is the result of "ping 192.168.1.2":
Code:
64 bytes from 192.168.1.2: icmp_seq=1176 ttl=64 time=0.244 ms
64 bytes from 192.168.1.2: icmp_seq=1176 ttl=64 time=1.31 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=1177 ttl=64 time=0.240 ms
64 bytes from 192.168.1.2: icmp_seq=1177 ttl=64 time=1.50 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=1178 ttl=64 time=0.243 ms
64 bytes from 192.168.1.2: icmp_seq=1178 ttl=64 time=2.57 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=1179 ttl=64 time=0.241 ms
64 bytes from 192.168.1.2: icmp_seq=1179 ttl=64 time=7.73 ms (DUP!)
64 bytes from 192.168.1.2: icmp_seq=1180 ttl=64 time=0.212 ms
64 bytes from 192.168.1.2: icmp_seq=1180 ttl=64 time=1.25 ms (DUP!)


and the result of "ping 192.168.1.1"
Code:
64 bytes from 192.168.1.1: icmp_seq=19 ttl=63 time=8.68 ms
64 bytes from 192.168.1.1: icmp_seq=20 ttl=63 time=1.82 ms
64 bytes from 192.168.1.1: icmp_seq=21 ttl=63 time=70.5 ms
64 bytes from 192.168.1.1: icmp_seq=22 ttl=63 time=1.26 ms
From 192.168.1.2 icmp_seq=20 Destination Host Unreachable
From 192.168.1.2 icmp_seq=21 Destination Host Unreachable
From 192.168.1.2 icmp_seq=22 Destination Host Unreachable
64 bytes from 192.168.1.1: icmp_seq=23 ttl=63 time=12.7 ms
64 bytes from 192.168.1.1: icmp_seq=24 ttl=63 time=2.59 ms
64 bytes from 192.168.1.1: icmp_seq=25 ttl=63 time=18.1 ms
64 bytes from 192.168.1.1: icmp_seq=26 ttl=63 time=7.88 ms
From 192.168.1.2 icmp_seq=24 Destination Host Unreachable
From 192.168.1.2 icmp_seq=25 Destination Host Unreachable
From 192.168.1.2 icmp_seq=26 Destination Host Unreachable


The DUP! packets disappear when the client is not connected to the AP.

When the units are set to WDS AP and WDS Station these strange patterns also disappear.
dejvid
DD-WRT User


Joined: 26 Sep 2010
Posts: 94

PostPosted: Thu Nov 11, 2010 17:51    Post subject: Reply with quote
I guess it is not as interesting as I thougt... Very Happy
dejvid
DD-WRT User


Joined: 26 Sep 2010
Posts: 94

PostPosted: Wed Nov 17, 2010 18:42    Post subject: Reply with quote
Tried again with version 15747 and the problem persists.
Client bridge suffers from DUP packets and WDS Station is unstable.
cowbs
DD-WRT Novice


Joined: 13 Nov 2010
Posts: 6

PostPosted: Thu Nov 18, 2010 8:14    Post subject: Reply with quote
dejvid wrote:
Tried again with version 15747 and the problem persists.
Client bridge suffers from DUP packets and WDS Station is unstable.


I see similar behavior with the WNDR3700 in client bridge mode. Response packets come fine over the air to the wired client but the router also decides to send network unreachable as well.
dejvid
DD-WRT User


Joined: 26 Sep 2010
Posts: 94

PostPosted: Thu Nov 18, 2010 9:52    Post subject: Reply with quote
Kind of good to see that I am not alone...I hope this issue will get resolved eventually.
cowbs wrote:
dejvid wrote:
Tried again with version 15747 and the problem persists.
Client bridge suffers from DUP packets and WDS Station is unstable.


I see similar behavior with the WNDR3700 in client bridge mode. Response packets come fine over the air to the wired client but the router also decides to send network unreachable as well.
baojia
DD-WRT Novice


Joined: 11 May 2008
Posts: 34

PostPosted: Thu Nov 18, 2010 18:25    Post subject: Reply with quote
forget it, changed to openwrt, works fine`
mksm
DD-WRT Novice


Joined: 29 Apr 2011
Posts: 1

PostPosted: Fri Apr 29, 2011 4:46    Post subject: Reply with quote
Hello,

About 2 hours ago I found this topic as I was having the same issue - duplicate pings with client bridge and flaky routing to the internet on main router.

Btw, i'm using a Linksys WRT54GL as main router and TPLink WR941ND as client bridged. Network is G only.

Well, what fixed for me is activating Setup>MAC address clone. I had noticed that LAN/WAN _AND_ Wireless MAC were the same, which seem a bit odd. So i enabled MAC address clone in the client router and now works perfectly.

Hope this helps.

mksm
Madnick
DD-WRT User


Joined: 28 Dec 2010
Posts: 79

PostPosted: Fri Apr 29, 2011 6:04    Post subject: Reply with quote
I had my WZR-HP-G300NH working pretty good with the 16144. The only issues were the wi-fi dropout every two days or so and the low troughput. I tried the newer releases, but they only made the troughput worse. I was using 40MHz turbo mode only with WPA2-PSK AES.
I got better transfer speeds with my old WHR-HP-G54 routers, so I reverted to the stock firmware using WDS.
Transfer speeds with the stock "user friendly" firmware are now back to what one would expect from a 300Mbps 40MHz channel width mode.

So I vote NO the client bridge mode is not working.

_________________
1x DIR-615 D3 (DD-WRT 15778)
2x WHR-HP-G54 (DD-WRT 14929)
2x WLI-TX4-G54HP (DD-WRT 13064 and autoAP)
1x WZR-HP-G300NH (joke right?)
AzuraelX
DD-WRT Novice


Joined: 07 Oct 2007
Posts: 47

PostPosted: Wed Jun 01, 2011 0:31    Post subject: Reply with quote
I guess I'm a victim of this - I re-purposed my DIR-825 as the client bridge for the consoles in the living room, having got my Belkin up and running again, thinking 5GHz throughput would probably help with some of the streaming issues I've had with my PS3.

No such luck - for the first few seconds after a client connects, it'll have full network access, from then on it's rather unstable, which results in pings like this:

MacBook:~ azurael$ ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1): 56 data bytes
64 bytes from 192.168.2.1: icmp_seq=0 ttl=63 time=4.187 ms
64 bytes from 192.168.2.1: icmp_seq=1 ttl=63 time=1.734 ms
64 bytes from 192.168.2.1: icmp_seq=2 ttl=63 time=1.734 ms
64 bytes from 192.168.2.1: icmp_seq=3 ttl=63 time=1.700 ms
92 bytes from 192.168.2.254: Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 dbf9 0 0000 3f 01 1a5c 192.168.2.2 192.168.2.1

92 bytes from 192.168.2.254: Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 0ec2 0 0000 3f 01 e793 192.168.2.2 192.168.2.1

92 bytes from 192.168.2.254: Destination Host Unreachable
Vr HL TOS Len ID Flg off TTL Pro cks Src Dst
4 5 00 5400 3c9c 0 0000 3f 01 b9b9 192.168.2.2 192.168.2.1

64 bytes from 192.168.2.1: icmp_seq=4 ttl=63 time=3.524 ms
64 bytes from 192.168.2.1: icmp_seq=5 ttl=63 time=2.304 ms
^C
--- 192.168.2.1 ping statistics ---
6 packets transmitted, 6 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 1.700/2.531/4.187/0.978 ms

It behaves exactly the same on 2.4GHz and 5GHz... (Or with both enabled for that matter - what would the actual result of this be - confusion, extra bandwidth or total fail? It doesn't seem to make any difference aside from the fact that pings are closer to what I see on 5GHz alone)

My old Motorola WR850G running DD-WRT works fine as a (rather slow) client bridge on the 2.4GHz networks of either the DIR-825 or Belkin (which being a modem/router is running OEM firmware) from the same location so it must be an Atheros bug?!

Edit: Interesting, from this end PC-LAN->F7D4401(Router)-WiFi5GHz->DIR-825(Client Bridge) pings show no issue whatsoever and I can navigate around the web interface on the remote DIR-825 no problem at all...

Ping statistics for 192.168.2.254:
Packets: Sent = 50, Received = 50, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 4ms, Average = 1ms

_________________
Current setup: VMDG480 (Modem Mode) > DIR-825 Rev. B1
kingweeelol
DD-WRT Novice


Joined: 01 Aug 2011
Posts: 1

PostPosted: Mon Aug 01, 2011 6:34    Post subject: Reply with quote
I had the same problem with trying to Bridge a WNDR3700 with dd-wrt. Let's just say that the connection was inconsistent (some packet loss and routing issues). Also, from what I've read this is not a unique problem, client bridges with Atheros chipsets appear to be unstable with dd-wrt. I ended up setting up a WDS system instead.

Instead of setting the network up like this:
AP (wndr3700v1 5ghz stock firmware) -------> Client Bridge (wndr3700v2 5ghz dd-wrt 17201)
I used WDS:
WDS AP (wndr3700v1 5ghz stock firmware) -------> WDS Station (wndr3700v1 5ghz dd-wrt 17201)

And it works flawlessly. Instead of intermittent request timed out and destination host unreachable the connection is steady.

I also tried using the mac address clone tool to no avail. Currently I'm running the latest build (17201).
Goto page Previous  1, 2, 3  Next Display posts from previous:    Page 2 of 3
Post new topic   Reply to topic    DD-WRT Forum Index -> Atheros WiSOC based Hardware All times are GMT

Navigation

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You cannot download files in this forum