Posted: Tue Jun 22, 2010 15:30 Post subject: Client bridge mode between Atheros and Ralink
Guys,
I have four wireless devices on my apartment:
One DIR-300 A1 (Atheros) as main router;
Another DIR-300 A1 and one Buffalo WHR-G125 (Broadcom) configured in client bridge mode.
One week ago I bought one DIR-600 B2 (Ralink) and intended to configure it as another client bridge.
The problem is that the DIR-600 is not estabilishing conection with the main router (DIR-300 A1). I have followed all the wiki steps for client bridge mode (except the part of setting the ack timing to zero, that I couldn't find it in the ralink dd-wrt firmware).
I also tried configuring the DIR-600 as main router. In that way, the Atheros devices could not connect to the DIR-600.
The wierd thing is that the WHR-G125 was able to connect to the DIR-600 without any issue.
All routers are flashed with BS's 14594 (except the G125 whitch is with Eko's latest build).
Has anyone managed to configure a DIR-600 as a client bridge in such a way?
[]'s _________________ TPlink TL-WDR3600ND as WDS AP
TPlink TL-WR841ND v9 as WDS Station
TPlink TL-WR1043ND v1.8 as WDS Station (with VAP disabled)
Typically ralink devices wont configure as client bridge, only client mode.
Some ralink devices wont establish a link between broadcom and ralink.
A lot of times when you are having interface problems its because of the protection mode (WPA, WPA2). broadcom routers don't like to interface well with atheros using WPA or WPA2.
Try turning the security off on both and try to establish communication.
Another thing is, make sure that all routers are set to the same wireless channel. Some firmware versions dont like to set the wireless channel properly, (they default to 1)
Instead of "joining" the network using site survey, try manually typing in the SSID and select the channel while in AP mode. Then change it to client bridge. (save then apply). That should set the ssid and channel to the right channel. If that works then try setting wpa or wpa2. _________________ 1x WRT610Nv2 big - 14280 NEWD-2 K2.6 BrainSlayer
1x WNDR3300 mini - 14205M NEWD-2 K2.6 Eko
2x AR670w std - 14289 v24
Brainslayer
1x AR690w mini - 15649 v24
Brainslayer
2x AR430W std - 13064 v24 Brainslayer
2x WNR834B v2 mini - 14311 K2.4 BrainSlayer
1x RT-N16 big - 14280 NEWD-2 K2.6 BrainSlayer
1x WRT54G V5.0 micro - 15704 v24 Brainslayer
1x WRT54GL V1.1 micro - 15704 v24 Brainslayer
Last edited by btechnet on Wed Jun 23, 2010 14:52; edited 1 time in total
Joined: 10 May 2008 Posts: 1380 Location: Pacific North West, USA
Posted: Wed Jun 23, 2010 13:22 Post subject:
Yes, I've seen the issue where the WHR-G300N (RT3052 based)
would not connect to a Broadcom router (Asus RT-N16)
What if you reconfigure your layout?
Put either the WHR-G125 as the main AP,
or put the new DIR-600 as your main AP
And then have the others connect to that? _________________ Soylent Green Is People !
=-=-=-=-=-=-=-=-=-=-=
Netgear Nighthawk R7000 - DD-WRT Build R46220
Linksys EA8500 - OpenWRT IPQ806x Trunk R16375 5.4 Kernel
Posted: Mon Jun 28, 2010 2:50 Post subject: Feedback
Guys,
Just to give you some feedback:
As you could see in my first message, I tried putting the DIR-600 as main router. In that configuration, only the G125 (Broadcom) could make the connection with it. The two others (DIR-300 A1) couldn't.
The solution for me was exchanging the DIR-600 that I had bought in another DIR-300 that was sub-utilized as an AP in my brother's school: Now I have 3 DIR-300 (2 in client bridge mode), all working without any issue.
[]'s
PS: Ah, the DIR-600 is working fine as an AP _________________ TPlink TL-WDR3600ND as WDS AP
TPlink TL-WR841ND v9 as WDS Station
TPlink TL-WR1043ND v1.8 as WDS Station (with VAP disabled)