Talk:Wireless Bridge

From DD-WRT Wiki

Revision as of 07:22, 21 April 2007 by Beveal (Talk | contribs)
Jump to: navigation, search

The 63 character key maximum in the instructions is not a bug. 63 printable characters = 256 bit encryption, which should be enough for WPA2.

Joker

--

I don't use MAC filtering on my network. Is that a required step?

--

The title is "Wireless Bridge", but the content is "Client-bridge". Why ? The term "Wireless-bridge" is usually used for connection of two APs (both running in AP mode), sometimes referred to as "WDS".

stein

Operating Mode must be set to Router

I was playing around with this today. It seems to only work if the Client-Bridge device is set to some type of routing and NOT set to Gateway under the Advanced Routing tab.

Set AP Isolation to disabled for the Host Router

Hi! Thanks for a great walk-thru! It worked excellent, except for one thing. My clients connected wirelessly with the host router was not visible for the computers connected to the client router. (And since all my computers use wireless connections, this was a little showstopper....)

But when I disabled AP Isolation on the Host Router, everything works fine!


I now have a KiSS VR558 connecte to a DD-WRT modified Linksys WRT54G(Bridge client), which connects wirelessly to my WRT300N (Host w/Internet access). My main computer where all my movies and music is located, is wirelessly connected to the main WRT300N via a WMP300N. It is now accessible from the KiSS via the brigde and main router.

Thanks again!!

WPA not working on WHR-G54S bridge with Actiontec AP.

Great summary, except I can't get the client-bridge working using WPA-PSK. WEB works fine, though. My bridge is a Buffalo WHR-G54S running DD-WRT v32 SP2 and my AP is an Actiontec MI424-WR (supplied by Verizon FIOS). WPA otherwise works with the AP. I can connect using WPA-supplicant just fine.

The bridge seems to associate with the AP in WPA mode, but there are 0 packets in or out. The AP logs cryptic errors:

  • Apr 21 00:10:20 2007 System Log Message kern.debug Clink Reset Cause :0x1b0002 Reg:0x20000 Dbg:0xa9b
  • Apr 21 00:10:16 2007 System Log Message kern.debug Clink Device Forced reset
  • Apr 21 00:10:05 2007 System Log Message daemon.warn cLink: clink0: ioctl(DRV_GET_MY_NODE_INFO) failed, res=-1: Bad address.
  • Apr 21 00:10:00 2007 System Log Message kern.debug Clink Reset Cause :0x1b0002 Reg:0x20000 Dbg:0xa9b

Again, in WEP or unencrypted mode, the AP sees it fine. Do you think it's the bridge or the AP? Any ideas?

Beveal 09:21, 21 Apr 2007 (CEST)