Bug 1629 - wpa fails with draytek vigor 2600 series routers
: wpa fails with draytek vigor 2600 series routers
Status: CLOSED FIXED
Product: SB 2/3
Classification: Unclassified
Component: Wireless
: 13
: All All
: P2 normal with 1 vote (vote)
: ---
Assigned To: Blackketter Dean
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2005-06-03 15:45 UTC by Kevin Pearsall
Modified: 2009-09-08 09:29 UTC (History)
3 users (show)

See Also:
Category: ---


Attachments
draytek dump--vidur may need to comment on the contents (346.10 KB, application/octet-stream)
2005-08-09 13:17 UTC, Kevin Pearsall
Details
second draytek dump marked deauth--vidur?? (374.35 KB, application/octet-stream)
2005-08-09 13:17 UTC, Kevin Pearsall
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Pearsall 2005-06-03 15:45:28 UTC
reproduced here.  the mac mini can connect, but sb2 with fw13 can not.
Comment 1 Greg Siemon 2005-06-03 19:03:45 UTC
Can connect via WPA with Netgear WG311T but SB2 fails on Draytek 2600G
Comment 2 Kevin Pearsall 2005-06-29 16:44:22 UTC
oh no, did this not get fixed??
Comment 3 Vidur Apparao 2005-07-11 10:15:32 UTC
Urgh...spent many hours trying to debug this to no avail. The problem seems to
be in the 4-way handshake that's part of the start of a WPA session. The Draytek
AP reports a "TKIP frame error (MIC)" and then times out on the handshake. This
is in response to the EAPOL key response (the 2nd in the handshake) from the SB2.

This is similar to problems noted in:

http://forum.draytek.com.au/index.php?showtopic=725 and
http://forum.2-com.de/draytek-vigor-thema2838.html

I've also noticed that with firmware 2.5.6, the Draytek AP seems to send the 3rd
handshake packet immediately after the 1st, without waiting for the response
from the station. This doesn't seem to happen with 2.5.4, but the MIC error
still occurs. I tried going back to earlier firmware revs, but had problems
getting the WLAN to work at all.

The MIC (Message Integrity Check) generation algorithm is fairly well
established, so I'm not sure what the problem would be...especially since we
work perfectly well with other APs that support WPA-PSK. The frame generated by
the SB2 itself seems to be identically structured to those from another station
(a Mac laptop) that was able to successfully connect.

If anyone has success installing and testing with Draytek firmware revs under
2.5.4, I'd be curious to know the results.
Comment 4 Blackketter Dean 2005-07-11 10:27:52 UTC
Sounds like a bug in the draytek.  Has somebody contacted their support folks?
Comment 5 Greg Siemon 2005-07-22 06:40:59 UTC
Submitted a bug report Draytek Taiwan.  

Draytek Ticket Number is 2005071810000337

Got a reply asking for:
1. The 2600G's config file.
2. The user Manual of the Squeezebox2.
3. Please make some screenshots of the WLAN settings on the Squeezebox.
4. Please capture packets while you're connecting Slim to Vigor with WPA
encryption, then mail it to us.

I did 1, 2 & 3 but I have directed them here and asked them to contact Vidur for
ethereal logs as I can't set my network adapter to promiscuous mode under Windows.

Hopefully we can get this resolved.
Comment 6 Kevin Pearsall 2005-08-09 13:17:11 UTC
Created attachment 707 [details]
draytek dump--vidur may need to comment on the contents
Comment 7 Kevin Pearsall 2005-08-09 13:17:39 UTC
Created attachment 708 [details]
second draytek dump marked deauth--vidur??
Comment 8 Blackketter Dean 2005-08-17 17:35:05 UTC
Vidur to update Draytek on the issue.
Comment 9 Richard Titmuss 2006-04-19 16:34:07 UTC
I have been testing with a Draytek vigor 2800 and WPA and WPA2 are fixed in firmware 43. I assume this means the vigor 2600 will now also work. This version is now in test and should be released tomorrow. Please re-open the bug if you still have problems once the new firmware is released. At the moment the WEP+WPA mode in this router does not work.
Comment 10 des 2006-04-20 13:39:03 UTC
Firmware 43 is working with WPA2 on my Draytek 2600G using modem firmware 2.5.7
Comment 11 Chris Owens 2006-05-31 11:53:09 UTC
This bug was fixed with the 6.2.2 release which included fw48.  If anyone is still having issues, they can re-open the bug.