Still doesn't work. Won't connect to another DD-WRT running router over mixed G/N network. What driver are you using in these builds? How can you release a product or firmware that doesn't provide the most basic advertised functionality? And on a side note, why is the release date on the support website still listing June, when the latest professional build was released only recently. Sloppy!
WHR-HP-G300NHs connect to identical chipsets for WDS, as in, another WHR-HP-G300NH. chipsets with only G will have a different chipset and are not compatible for the WDS feature.
Not talking about WDS, talking about wireless bridge. Both routers are Broadcom chipset, and are wireless N. This is a serious problem. You all maintain that DD-WRT is supported, but in the real world only limited functionality is possible. Either get it working, or stop inducing people to buy a product with fraudulent claims.
nchall, I'm having what sounds like the same problem. I'm trying to bridge two WHR-HP-G300N and having no success. Both are running DD-WRT v24SP2-EU-US (08/19/10) std
(SVN revision 14998) (though I did have trouble flashing the secondary router) and my primary lists the secondary as a wireless client.
Primary: WHR-HP-G300N
SSID: UberWAN (don't judge me, lol)
WPA2 Personal TKIP + AES
AP Mode, Channel 9
Secondary: WHR-HP-G300N
SSID: UberWAN
WPA2 Personal TKIP+AES
Client Bridge Mode, Channel 9
Gateway set to Primary router's IP
I've tried running a virtual interface and not on the secondary, neither works. If there's anything else I can try, I'm at my wit's end.
First, try reflashing the FW on that second AP, in case the first flash was not 100%.
Then,try setting up in the simplest bridging manner first, without security, just to verify the WDS/wireless bridge between the two WHRs is working. If working, add security next and reverify connectivity.
UberWAN - cool name!
I'm not sure what the simplest bridge would be. I'm not sure how to set up WDS using the Buffalo DD-WRT. Would trying the client bridge mode without security be simplest? Is there another way to bridge them? I'm pretty inexperienced with all this, so I've been going by what I've read on these and the DD-WRT forums.
The methods I've tried are:
http://www.dd-wrt.com/wiki/index.php/Repeater_Bridge
http://www.dd-wrt.com/wiki/index.php/Client_Bridged
I'll try reflashing the secondary again, I really hope it's just a bad flash. I didn't think that was it because, aside from completely failing to work, it's been working fine. lol By that I mean the interface, etc.
Thanks for the timely response, drmemory. I'll post results of my reflash and unsecured attempt at bridging using what I tried before.
here's a link to basic WDS/bridge setup
You're welcome - just want you to get your setup in place and working.
I started my setup before your reply was up, drmemory, so I'll report what I've gotten from that.
I reflashed a couple times; the first didn't seem to go well. After starting the upgrade, it seemed to go fine. When it finished, though, I couldn't connect to 192.168.11.1 anymore. I waited a bit before trying again but couldn't. So I reset it which allowed me to connect, then upgraded again. That time it seemed to go through fine.
Now I've configured my primary and secondary as before; same SSID and channel, but no security. The client router shows on my primary under status > Wireless as a client. However, I can't connect to the client's IP (which isn't the same as the primary) and the client can't connect to anything.
I've looked at the basic setup that you linked to but I'm afraid I'm not sure what those instructions would translate to under DD-WRT. I'll give it a shot, though. About the WDS setup: how is it different from a client bridge? And what wireless mode should the router and client be set to (WDS AP and WDS Station are my options for WDS, otherwise it's client, client bridge, AP or ad hoc)
So to answer nchall's question if your using a DDWRT version of Buffalos WHR HP G300N your NOT using a broadcom chipset its is in fact a Atheros ar7240 and this is most likely the issue. We are attempting to work with DDWRT to resolve this "issue". However at this time we do not have an ETA.
If you are using both Atheros chips sets here is a walk through.
Introduction
WDS on the Atheros-based routers(WHR-HP-GN and WHR-HP-G300N) works much different than the Broadcom-basedrouters (WHR-HP-G54 and WHR-G54S). On Atheros chips, the only way to do WDS isfor the repeaters to work as clients. In the normal Buffalo firmware, it'spretty easy to set up. It's much more involved on DD-WRT.
NamingConventions
In this How To, the terms used aredifferent than what you may be used to, so I'll explain them here first:
Gotchas
Be careful of a few things when youset this up.
SettingUp WDS
Start out with a computer wired intothe AP.
AccessPoint (root router)
AP Basic Wireless config
Easy Part:
WDSStation(s)
WDS Station Basic Wireless config
This is the harder part:
Testing
WDS Station Wireless Node Status
drmemory, paul, thank you guys so much for helping me out. Paul's setup seems to be working great. My down/up on the client end is about 3mbps for both (per speedtest.net), is that what I should be expecting? The router is giving me 9 down and 3 up. Terrible, because I'm paying for 24 or something like that.
Thanks again!
"We are attempting to work with DDWRT to resolve this "issue". However at this time we do not have an ETA."
Don't you think this is a problem? You advertise that this router supports DD-WRT but it clearly doesn't, and you don't have any idea when you will fix it! Sounds like a false claim to me.
** the thread question was answered in page one of this thread - how to setup wireless Bridge configuration (correction - how to set up WDS). If you have questions about how to use other features.If the explanation doesn't work for you, describe why, in enough detail to where we can duplicate your symptoms, and provide a fix, or send a bug report.
you may want to try to change the channel, and or even try moving the AP closer to the router (at least for testing). Also what is your client capable of (N, G, B, ect..) Make sure all the devices have the latest firmware as well
sorry but the thread question has not been answered, and furthermore i started the thread. currently there is no way to wireless bridge with this router running dd-wrt that gives an acceptable user experience. as stated above, there is no eta for when this issue will be fixed. not sure why issue was put in quotes as it is most certainly a real issue.
Did you set up as per Paul's instructions - if so, list your data and explain what's going on in your system, so we can try to duplicate, then either provide an answer or push it up as a bug.
I don't see how setting up the router using WDS "solves" his problem. He is asking for the bridge connection to be set up, but only instructions for WDS has been provided.
I agree, and am having the same problem. Please provide us with clear instructions on how to get a second router to properly BRIDGE with the first router, not just to be used as a repeater through WDS...
I want this second router to bridge the same subnet wirelessly and allow wired clients on the far side to have full access to the subnet/network. So far, this has not worked.
PixelFreak wrote:I don't see how setting up the router using WDS "solves" his problem. He is asking for the bridge connection to be set up, but only instructions for WDS has been provided.
I agree, and am having the same problem. Please provide us with clear instructions on how to get a second router to properly BRIDGE with the first router, not just to be used as a repeater through WDS...
I want this second router to bridge the same subnet wirelessly and allow wired clients on the far side to have full access to the subnet/network. So far, this has not worked.
See if this helps You any>> http://www.dd-wrt.com/wiki/index.php/Repeater_Bridge#Atheros
However WDS should accomplish the same results via wireless. If you want to connect a wired Bridge follow the steps below
Disable the wan port in set up
Set a static IP within your existing subnet
in Advanced routing change the operating mode to Router
Then use the lan port to connect to the network.
Save your changes
the problem is with the madwifi driver dd-wrt is using, so until that is resolved pointing us to a poorly maintained wiki is less than helpful.
most of the people on here are fairly technical and if we are having these problems buffalo should certainly do more than "bump this up as a bug". you've clearly advertised functionality that doesn't exist at present, and certainly didn't when the item was sold. i would advise you to address this quickly as remedies become exponentially more costly and your options decrease farther down the line.
I have 2 Buffalo routers that use ddwrt at home, both are configured to use WDS, and both work as advertised. I am able to connect them wireless and use the Ethernet ports on the AP as well as the router. This is how I stream my media from the computer room to the downstairs TV room. DDWRT posted that this is only designed to work with the same chipset. Buffalo has only advertised that it comes with DDWRT. I think your argument is with the wrong company. Now that said, I have no issue reporting that to my management that this is a HIGHLY requested issue and I will push to get it resolved as quickly as possible. Also since we are all fairly technical people we also should respect DDWRT for what it is, an open source platform that has opened the doors for many things. I will continue to work out as many issues as we can with both Buffalo and DDWRT.
this is from the buffalo press release announcing the new routers:
"Buffalo’s new DD-WRT enabled high power router and access point offering will include WZR-HP-G300NH, WHR-HP-G300N and WHR-HP-GN, all delivering three-in-one functionality that is unmatched in the market. These new wireless solutions can either function as a high power router and access point, a wireless bridge or as a universal range extender. Uniquely, when operating as a universal range extender, all of Buffalo’s DD-WRT enabled wireless solutions can connect to any router, regardless of brand, greatly extending the range of wireless coverage, eliminating ‘dead spots’."
clearly refutes your earlier point. all i am asking for is the basic functionality that was behind my purchase decision. i can no longer return the item as i have been waiting for you all to fix this issue and 30 days have elapsed.
I've been using the setup Paul described on p.1 of the thread and all was working fine until recently. For the past couple days I've been getting ~500kilobits/s connection speed with intermittent spikes to ~3megabits/s. I've checked with my ISP and tested my connection through the modem; not great, but about 10megabits/s. I've power cycled about everything connected to either G300N and I can't seem to resolve this issue.
The only change I made from Paul's instructions was to enable uPnP in the hopes that my XBox would stop giving me it's "I don't like your NAT settings" problem. It didn't, incidentally.
Did enabling uPnP drop my LAN bandwidth to nothing, or are the issues seperate?
Well, as far as I can tell the uPnP settings didn't affect anything. Enabled, the XBox still has connectivity problems. Disabled, bandwidth through the routers (either) is barely 10% of what it is when using just the modem.
I would really appreciate some assistance on getting my network speeds back up. I've got a tech from my ISP coming today but I'm pretty certain he won't find any problems with my modem or signal.
i have to agree with earlier posts in this thread .. the functionality does not work as advertised .. i am using wds between two whr hp gn models .. to say its been frustrating is an understatment .. firstly can paul or dr memory confirm theres an issue with dhcp when using wds in the described setup in this thread .. i find i can connect on once and then no more from the client end of the wds .. ping still works from the command within the client wds router and can ping the master .. i have no signal strength issues as i am getting 20 to 40 % strength .. paul dr memory should i open a new thread for this issue .. using 14998 ddwrt on both routers .. problem dhcp via the client AP in wds does not work after connecting once .. setup is as follows
wds ap encryption on ( WPA AES ) dhcp on static ip
wds client encryption on ( WPA AES ) dhcp off static ip and wan connection set disabled and dns & gateway pointing to wds ap static address
virtual interface enabled on wds client same settings as wds AP ( also in AP mode not wds AP )
DHCP lease comes through once and never again until both routers are rebooted ..
Further reseach indicates this is issue with dhcpd daemon in WDS ap unit ( lots info on this in google as you cannot delete a lease from the dhcp database ) .. a work around is to use DNSmasq instead which i tried and it would not work .. can someone at least confirm this is a known issue as i have wasted so much time on this and just keep getting disappointed .. paul dr memory please make a suggestion
padraig
I have almost the exact same set up, with an exception to the security I use TKIP only.
I will over the day or so make the necessary changes to try to replicate your issue. How far apart are your routers and what channel are you using?
Paul thanks for the quick response .. i have just returned from the client where they are installed .. uptime was 7 days .. anyone with the key could connect to the master AP .. the client AP would not accept connections at all .. i tried 3 different laptops while onsite .. all the same fine on the master but maybe work on the client ap
during the initial config phase of this setup .. i tried tkip, aes and aes+tkip and had the same issue .. the routers were a room apart .. i also had different SSID for master and client AP ..which you posted was a requirement for correct operation in this thread .. but it still happened .. then i tried to operate in mixed mode only still the same ( my preference is for NG mixed in order to compensate for the reduced throughput in WDS mode but this is flexible if i can get it to work )
After much research i did a 30-30-30 on both routers and reconfigured no success .. i tried DNSmasq and could not get it to work at all
I also found that it would not work at all until i added the mac address to the wds tab
moving routers onsite the routers are 3 rooms apart and get 10 to 20 signal on the client mac under the wireless status page .. ( NG mixed mode .. mixed mode only give 5 to 10 % signal ) .. before installing i did a full channel scan using inSSider and put them on channel 1 using upper channel for control channel ..i still cannot figure it out
The LAN and WAN domain settings are not required AFAIK as i have set these up without any difference
Can u confirm that the VAP setting for SSID must be different to the Master AP in WDS mode and also do the WDS tab have any use at all
Many thanks again for your assistance
Padraig
I bought my WHR-HP-G300N a few weeks ago from NewEgg. I intended to get an older one and install DD-WRT on it myself, but I sprung for the newer one with your "Pro" DD-WRT firmware on it instead.
This firmware DOES lack functionality. I spoketo a support professional about it, and it seems that Buffalo has a different definition of "wireless bridge" from the people who made DD-WRT.
What people here are asking for is a point-to-point wireless connection-- a wireless router connected to a modem (not necessarily a WHR-HP-G300N, or even necessarily a Buffalo router, as I believe is the case for nchall) being connected to WIRELESSLY by a Buffalo router with DD-WRT (WHR-HP-G300N, in my case) and relaying a connection to clients wired into it. This is possible with other routers running DD-WRT, without any implementation of WDS, using the "Client Bridge" setting under Wireless configuration.
I'm running this sort of setup on a bunch of Linksys WRT54G routers now, but the Client Bridge setting on my WHR-HP-G300N doesn't do this. It doesn't seem to do anything. This is a problem that YOU, Buffalo, need to solve.
Buffalo -- I was excited to see formal DD-WRT support and bought 5 of these puppies. However, my faith and fervor for your experiment into DD-WRT is starting to fizzle.
Not necessarily because you don't support Client Bridge mode, but that you allow it to be a selectable option. I doubt that I'm the only guy who has spent 3 weeks banging his head at the DD-WRT site, trying to figure out what I'm doing wrong in trying to get Client Bridge Mode working.
If you guys don't address the issue, can you please have the decency to remove it as an option?
So I tried the WDS like suggested. It seems super flakey without a precise power up sequences. I've never had to deal with making sure my customer installations boot up one router prior to the other in order to operate properly. The DD-WRT Client Bridge Mode on other hardware just works reliably, and thus seems to be an advantage of Client Bridge. Do I have something configured incorrectly, or should I expect power outages at 4am when nobody's there to boot them just right to be a major headache?
One more thing -- So far, no matter what I do, I can't get the TX Power to go higher than 19 dbm (<100mw). Is there some magic unlocking mechanism to get the "HP" model to put out?
Thanks. I'll buy lots more if we can get a couple of these things worked out. I absolutely love that the antennae are replaceable.
My Tx Power seems locked to only 16 dbm! Editing the Tx Power option under advanced settings does nothing. Is using WDS a way to make my wifi devices talk to my ethernet devices over the lan?
I bought 2 of them one month ago because the AD said this model was great! But it's NOT!
It has wasted me lots of time... how can I return them? I think Buffalo must have a solution for customers. Either fix them, or recall them
I have a WHR-HP-GN and Client bridge does not work! I have a linksys wrt54g that is running dd-wrt and it connects to my AP just fine. I did identical steps on this POS and it says its connected, my AP lists it as a wireless client, but I get no internet access. This is a huge flaw and has wasted hours of my time. I will be returning this to newegg and leaving a review to warn others not to waste hours of their life on faulty buffalo products. If someone from Buffalo would like to rectify this please feel free to email me.
I'm having the same problem. I see a connection between the 2 points but get no internet from my WDS AP, only the WDS station. I don't understand!! I don't want to waste anymore time if this hasn't been resolved and is a Buffalo issue. Please help!!
Please provide all details for people to be able to assist, or call the local Buffalotech support line, if you want immediate help without supplying enough details.
I just bought two WHR-HP-G300N's and followed Paul's instructions on page one to set up the bridging between them. It almost works, but the wireless client only stays connected for 2-7 seconds then drops. I've changed wireless channels, different modes etc with no changes. Prevoius experience with Linksys 54G's running DD-WRT was not this difficult. Should I regret this purchase?
"Should I regret this purchase?"
If you want to use DD-WRT, then yes you should.
Revert to the "user friendly" firmwares on both units and use WDS
BillGiles, if you want to PM me your contact information I can call you and walk you through the set up.
I bought the G300N based on its advertised claims for the sole purpose of being a wireless bridge in my home network so as to add internet access for my home-theater components in my downstairs . LIke others, I have spent many hours trying to configure my WHR-HP-G300N as a wireless bridge. My AP is a Linksys WRT310Nv1 router, which does not support WDS, so I do not have that option. As others have posted, I can see the G300N as a client on my 310N, so I know the wireless is setup properly (it will get an IP address in Client mode as well). My laptop gets IP addresses from the G300N if DHCP is enabled, so I know the router side of things is working. Obviously the packets are not getting routed or forwarded to/from the radios MAC to the router.
I am very adept now with the process: Factory (hard) reset; Change IP address and gateway. Release IP address on laptop to work on changed subnet; Change wireless configuration to match 310N (I always check to make sure the radios are connected). Reboot. Change to Client Bridge. Change Firewall settings; Change Gateway to Router. Save; reboot; Rinse and repeat, changing up the order once in a while just to keep things fresh (basically following http://www.dd-wrt.com/wiki/index.php/Client_Bridged instructions).
My assumption is that the router (eth0) and the wireless (ath0) interfaces must be bridged, or a static route must be set up between them to make this work, which Paul hints at in his instructions earlier in this thread, but the internal bridges apply to WDS configurations and I can't get it to work. I have tried many combinations, trying to think "logically" through the process, and while I know some about networking, I don't know enough to fully understand the interconnections and the internal neworking configurations and routes and what I should be seting up. Of course, I shouldn't have to for setting up a basic, "advertised" capability.
I have the original box out and am getting ready to send back to the store and buy a router that will actually work and doesn't require a bottle of aspirin for setup. However, I thought I would try a deperation cry for help before doing so.
Let me ask the most fundamental question to the Buffalo folks: Can the G300N ever work as aClient (wireless) bridge with a WRT310N (Broadcom Chipset BCM4785), or, as it was advertised, any brand of router? If not now, wIll updates to DD-WRT allow this?
And BillGiles and Jotin, if you have some insight, can you please post. Curious to see if you were able to get it working.
Thanks for any feedback,
-Paul C.
My parents live in the boondocks and use a 3g wireless AP for their internet. I used a Buffalo WHR-HP-G300N as a repeater to extend the range of the Verizon 3g device which is only around 30 feet. I was originally having a lot of difficulty with the Buffalo DD-WRT firmware. I used the following procedure to use the Buffalo router as a repeater to extend the wireless network under a new SSID. I also found out that the Client Bridge mode seems to be the only way to make a true repeater and it is like the repeater mode that is used a Broadcom based routers. Regular client mode will only connect the original LAN to the router wirelessly but will not rebroadcast the signal.
This procedure worked for me.
General instruction: Religiously Follow the wiki for the generic Buffalo procedures in firmware update.
You MUST do hard reset INCLUDING change login/password before/after firmware update. I used the latest (V24 SP2 [beta] build 14896) as the router database recommended. I used the firmware upgrade section of the Buffalo DD-WRT to change the firmware to DD-WRT build 14896.
Set the router power switch to ON always (not AUTO)
Assuming you successfully loaded the two firmwares "buffalo-to-dd-wrt_webflash-MULTI.bin" first or "whr-hp-gn-firmware-MULTI.bin".
1. Hard reset the router. Change login name/password as necessary.
2. Settings-Basic. Disable WAN. Save.
3. Settings-Basic. Disable DHCP. Save.
4. (VERY IMPORTANT)Status - Wireless. Site Survey, select the AP you want to connect. Save. Apply.
6. Wireless - Basic. Here the Mode is "automatically" set to CLIENT. Save.
7. Disable Firewall. Save. Apply.
8. Basic - Advanced routing. Set to ROUTER. Save. Apply. WAIT FOR ABOUT 3 MINUTES as the router will connect/disconnect about 3 times.
9. Set PC LAN to DHCP
10. WAIT for at least 5 MINUTES. Sometimes, getting an IP address from the AP takes time.
===========
Continue here if you want to use as a repeater:
11. Change PC LAN TCP/IP to 192.168.1.10 Login to dd-wrt again (192.168.1.1)
12. Wireless-Basic. Select Mode to "CLIENT BRIDGE". Add a VIRTUAL INTERFACE. SSID should be different. The default is dd-wrt-vap. See note 1 below.
Mode: AP. Save. See note 2 below.
13. (OPTIONAL) Wireless - Security. You can add encryption/authentication here. Save. Apply. WAIT FOR ABOUT 3 MINUTES as the router will connect/disconnect about 3 times. Note: If your original LAN has security then the virtual interface will not work until security is entered under the physical network in wireless security.
14. Set PC LAN to DHCP
15. WAIT for at least 5 MINUTES. Sometimes, getting an IP address from the AP takes time.
I have used dd-wrt client bridge modes with Linksys and Asus Broadcom-based routers, but did not use them to create repeater, i.e. without creating virtual interfaces.
I did use two WHR HP G300N recently to create a WDS AP and a WDS station to create a bridge. I did not intend to use the WDS station as a repeater. However, I found out the unit tended to disconnect easily without creating a virtual interface. I have tried to use strictly client bridge (without virtual interface like jleable did), but I never get a proper connection that way. WDS AP and WDS station seem to work best for me, but it seems that I had a occasional disconnect if I specifcy AP to be g/n mixed mode and station to be n only mode. After I specified n only modes in both, the units remain connected after three days.
I notice today that there ia an alpha version for dd-wrt in the download area today. I have heard for quite some time that a new version will be forthcoming to solve some bugs in the bridge mode. Does anybody know what this alpha version fix?
Try to update the firmware to alpha version of 16753 using dd-wrt web interface - firmware upgrade under administration.
Try many times, but each time after a few seconds, it said upgrade failed. Another disappointment with Buffalo - first they list client bridge and client as optional modes but never worked for me. Now they post an firmware update that cannot be flashed into the unit.
I certainly would like to know if somebody is able to upgrade to this alpha version and try to see if client bridge mode works (without virtual interface) or not.
Just noticed that the file has been changed for this alpha release, judging from the file name of the firmware. It was ....1653...-eu-us.enc instead of .....16753...-eu-us.enc now. Will try again tonight when I get home.
The new firmware 16753 now can be flashed to the unit successfully. The client bridge mode still does not work. It looks like there was some changes to this mode as the menu, unlike the other dd-wrt versions I am familiar with, asks for default GW (I guess that means gateway) mode - either auto DHCP or manual. If manual is specified, then one needs to specify an IP for the gateway. I tried various way but still could not connect in client bridge mode to another WHR HP G300N as the AP.
WDS AP and WDS station pair still works, but I do not know how that affects the bandwidth. I have two other Netgear WNR2000 running with TOMATO connecting to the WDS AP too and I wonder if they are affected if the master is WDS AP instead as AP.
Well, if someone knows how to connect the G300N as a client bridge, please let me know how.
Apologies for the (incredibly) lengthy delay. Had some unfortunate life issues come up. My network hasn't changed in either set up or performance. I've just come back to try to resolve this issue, hopefully that's still possible.
My routers are still configured per Paul's walkthru, using Channel 9. Both are running the same firmware ( DD-WRT v24SP2-EU-US ) which I suspect is outdated but haven't had time to update. My upstairs router is connected to my cable modem, the downstairs router is the AP. I'm guessing the two are ~30' apart as the crow flies and much of that seperation is an open staircase, not solid wall.
Thunderous silence about the latest Buffalo DD-WRT build - v24-SP2 build 17135 posted 2011-06-06 - for Client Bridge. My first attempt with the new firmware failed. A google search of WHR-HP-G300N + "client bridge" returns failures, not successes. To be charitable perhaps those who successfully configured WHR-HP-G300N for client bridge just don't write about it.
Disappointing the Buffalo people in this thread who ignored client bridge, writing instead about WDS mode and pointing to instructions for the WHR-HP-G54 - as if the models were similar and instructions appropriate! ??
?Ah, yes I should write something about myself as this is my first post with this user ID.
I've been an IT consultant for several decades. I've used and deployed Buffalo AP/routers for almost a decade. My good experience with Buffalo AP/routers made them my top choice. That is until I went through the same problems as others reported in this thread.
Does anyone have successful experience making client bridge work on the WHR-HP-G300N with the latest firmware 17135?
My 300N v2 is working as a client bridge. Firmware: DD-WRT v24-sp2 (06/30/10) std?
It is from DD-WRT page. I have tryed new versions and they not worked. But this worked from first try.
Bad thing is that fw isnt stable to my liking. I need to reset it almost every day as WIFI connection to router is lost. I have heard that autoreset can be set though.
May be there are better firmware but I was tired to investigate after this worked.
What is the build number on the one that worked for you? I have heard that 13535 worked, but it looks like you might be using 14684. Please confirm the build number that is working for you.
I think it is despicable that Buffalo is selling these units as DD-WRT ready, when in reality, most of the functionality that is off the beaten path for routers flat-out doesn't work with DD-WRT. Buffalo, if you care, you need to get your buns down to wherever the good people making DD-WRT live, and have a conference with them in which code is written, analyzed, and tested until you have a 100% working DD-WRT for Atheros.
Either that, or go back to Broadcom chipsets going forward and offer to exchange all the Atheros units free of charge.
I know this: Linksys equipment hasn't looked so attractive to me in years.
I am using build 19154. Client bridge does not work for me, a frustrating experience like so many others have reported in this thread using earlier builds. I did find a temporary workaround. Telnetting to the Buffalo unit I noticed that the nameserver in /etc/resolv.conf was the same IP address as the address assigned to the unit. With this nameserver address I could not ping even the gateway router. I changed the nameserver address to the one I wanted using vi. Then I rebooted the gateway router and within minutes I could ping anywhere. And pinging through the night showed that the connection was stable. BUT the moment I rebooted or powered down and up the unit, or saved or applied settings from the web interface, the nameserver setting reverted back to the unit's IP address and I could no longer ping outside the unit any more. So if after any power failure or any configuration change or reboot from the web interface, I am willing to telnet in and change the nameserver back and reboot the host router, then the Buffalo unit works as a client bridge. It would seem that there would be a simple way to fix this problem. I tried to permanently change /etc/resolv.conf trying to remove the symlink to /tmp/resolv.conf but was unsuccessful because the /etc directory seems to be read only. If I can't find a permanent workaround I shall have to return this unit to the store.
I tried with newest build I found build 20119. It seem to have same problem that Client Bridge works through LAN but not with WLAN. It has the same problem that /etc/resolv.conf points to router itself.
Anyway by setting Wireless-"Basic Settings"-"Default GW Mode" to Manual and then defining my internet router as gateway, it seem to work.
It also works by setting "echo nameserver xx.xx.xx.xx>/etc/resolv.conf" (xx... is of coarse my internet gw ip) in Commands "Save Startup". Then /etc/resolv.conf will be updated on reboot.
With both method there still seem to be some problem with name resolution. With new pages it almost allways first fails, but works with try again.