Joined: 08 Jun 2006 Posts: 256 Location: Netherlands, Hengelo ov
Posted: Fri Aug 01, 2008 12:48 Post subject: WDS WPA2 personal working with the last builds (V24-SP1)
WDS with wpa2 personal AES was never working, (only wpa personal AES) til the last builds from V24 sp1. Build 10011 (Sebastian) and 10061M TNG Eko. Use the normal install instruction for WDS (see Wiki) I test it on channel 1, 6, 9, with several routers (wrt150N,wrt54g V2.2,wrt54gs v1.1, WRT54GL. Also with 1 master (router)(wrt150n V1.1) and two wds connections (wrt54G V3.1 an V2.2) _________________
1 E3000 AND 1 E2000 WPA2 AES
DD-WRT v3.0-r31277
Last edited by snooze7555 on Fri Aug 01, 2008 15:53; edited 4 times in total
for some reason - i cannot for the life of me get this to work. tried the latest builds referred to in here - and its between a dd-wrt and airport extreme. tried AES, TKIP, AES+TKIP... etc. problem is the airport doesntallow regular WPA anymore... only WPA2 mixed and WPA2....
WDS did work with WPA2 on at least one configuration. I have been happily using WDS with WPA2/AES for nearly three months now to link up two buildings.
2 x Buffalo WHR-HP-G54 configured for WDS, no other AP clients
WPA2 personal + AES
DD-WRT v24 (05/16/08) mini - build 9513
I can't vouch for other configurations of course ...
yeah - im going to try and downgrade the various v24 builds to see if the wireless units can talk properly-- right now with a v24-sp1 and airport express i just get errors in the airports log like:
Jun 25 14:44:33 Severity:5 Deauthenticating with station XX:XX:01:9a:23:f6 (reserved 3).
Jun 25 14:44:33 Severity:5 Rotated CCMP group key.
Jun 25 14:44:33 Severity:5 Deauthenticating with station XX:XX:01:9a:23:f6 (reserved 2).
I've got the same problem. I've tried Open security, WEP 128, all work. WPA and WPA2 dont work.
I'm running DD-WRT v24 SP1 and Airport Express 6.3 (802.11g).
Here's my log output from AX:
Jan 1 00:00:00 5 Configuration updated.
Jan 1 00:00:05 5 Rotated TKIP group key.
Jan 1 00:00:06 5 Initialized (firmware 6.3).
Jan 1 00:00:15 5 WDS established with station 00:06:25:df:XX:XX.
Jan 1 00:00:16 5 Deauthorizing station 00:06:25:df:XX:XX [2]
Jan 1 00:00:29 3 Administrative access denied to ::ffff:192.168.1.3/5605.
Jan 1 00:00:38 5 Deauthorizing station 00:06:25:df:XX:XX [15]
Jan 1 00:00:45 5 Connection accepted from ::ffff:192.168.1.3/5607.
Jan 1 00:00:56 3 No address for NTP server time.apple.com.
Jan 1 00:01:00 5 Deauthorizing station 00:06:25:df:XX:XX [15]
Jan 1 00:01:09 5 Connection accepted from ::ffff:192.168.1.3/5614.
Someone had mentioned, in another thread, that certain dd-wrt firmware builds support wpa/wpa2 with certain core revisions of certain chips, while others do not.
It would be extremely helpful if someone who knows could chime in and let us all know which builds support wpa/wpa2 for wds modes on which chips / corerev's.
Someone mentioned TNG or EKKO builds then another mentioned NEWD builds (lol). So I am confused on the issue. It seems like there are a lot of forks from different people and no nice central information page explaining which firmwares use which core drivers versus which ones support wpa/wpa2 in all the modes.
Can anyone help clarify the issue? Thank you!
Well to provide what I know about my devices is that I have an Airport Express w/ 6.3 firmware and supports 54G wireless. The Linksys Router is v1.0 WRT54g. Yep its the oldie but goodie. I know its a BCM43x series chip from looking at the DD-WRT status page.
Obviously thats not compatible. I'd be curious to know what version of WRT54G is. I would love to get this working.
Someone had mentioned, in another thread, that certain dd-wrt firmware builds support wpa/wpa2 with certain core revisions of certain chips, while others do not.
It would be extremely helpful if someone who knows could chime in and let us all know which builds support wpa/wpa2 for wds modes on which chips / corerev's.
Someone mentioned TNG or EKKO builds then another mentioned NEWD builds (lol). So I am confused on the issue. It seems like there are a lot of forks from different people and no nice central information page explaining which firmwares use which core drivers versus which ones support wpa/wpa2 in all the modes.
Can anyone help clarify the issue? Thank you!
My understanding was that it was impossible for WDS to work over WPA2. I read that there was a bug in the driver, which isn't something that can be fixed by Brian/EKO/etc.
I had WDS w/WPA2 AES working great for a long time on v23 SP2 and then I upgraded to v24 RC7 and it worked great for the few months I used it until I saw that v24 SP1 was out yesterday. I tried it out and could not get WDS to work properly. The closest I came was I was able to access my other WDS router's config wirelessly, but that only lasted about 10 minutes. When I get home from work tonight I'm going to do a complete reset and hope for the best.
I've tried WPA+TKIP, WPA+AES, WPA2+AES all with my WRT54g main WDS and Airport Express WDS remote and it wont connect no matter what.
It does work with WEP 128 or without encryption. I dont know what the deal is. I read everywhere online that WDS and WPA work but nothing seems to show consistency.
i could not get v.24sp1 working in WDS with WPA AES either.
Link would crash or vanish after a unit reboots for what ever reason.
had v24 rc5 running before for month without a hitch.
downgrades to v.24 final and the wds seems stable again (sofar no issue anyway)
hardware for me is the whr-hp-g54
guess i wait for the next stable release and hope WDS works again :)
regards
tec _________________ 2x Buffalo WHR-HP-G300N in AP
2x Buffalo WHR-HP-G300N in WDS (not working atm)
1x Buffalo WHR-HP-G300N in Wireless Client-Bridge (not working atm)
1x Buffalo WHR-HP-G300N in Reserve (still looking for that on ebay)
I now have success with 3 WRT54GL's running v24SP1 using WPA2 Personal Mixed w/ AES connected together with WDS. I don't attribute the success to anything I did in particular. All I know is it took hours to finally get it to work and a lot of 30/30/30 and reinstalling the firmware. Good luck to anyone that is having trouble with this, but it is possible.