linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dave <kilroyd@googlemail.com>
To: Pavel Roskin <proski@gnu.org>
Cc: Dan Williams <dcbw@redhat.com>, Dave <kilroyd@googlemail.com>,
	linux-wireless@vger.kernel.org,
	orinoco-devel@lists.sourceforge.net
Subject: Re: [PATCH 00/19] orinoco: WPA for Agere based cards
Date: Wed, 06 Aug 2008 19:33:13 +0100	[thread overview]
Message-ID: <4899EE69.6050205@gmail.com> (raw)
In-Reply-To: <1217983050.19480.41.camel@dv>

Pavel Roskin wrote:
> On Mon, 2008-08-04 at 19:28 -0400, Dan Williams wrote:
>>> I'm not familiar with the difference between WPA/WPA2. Is that expected to work?
>>
>> But you might be able to get away with WPA2/RSN + TKIP if the AP allows
>> this configuration.  In that configuration, the only difference between
>> WPA and WPA2/RSN would be the information element IDs, really.  But if
>> the firmware itself doesn't say it supports WPA on whatever website it
>> came from, then likely the card won't do WPA2/RSN either.
 
The firmware supports WPA, but makes no mention of WPA2.

> I tried association to hostapd with madwifi, and the only working
> configuration is WPA1 only with TKIP.  Even enabling WPA1 and WPA2 and
> TKIP makes the connection fail.  Forcing WPA1 and TKIP in
> wpa_supplicant.conf doesn't help.
> 
> I looked at the patches.  They have references to TKIP, but not to CCMP.
> Yet it would be nice if we could support WPA1+WPA2, as we cannot require
> that access points stop supporting WPA2, which is the 802.11i standard.
> It's possible that we have an issue outside the driver.

I don't believe the firmware supports CCMP. It has support for CCX/CKIP (Cisco specific TKIP-alike), but I'm guess we don't care about that.

I suggest that we leave figuring out how to associate with a WPA2+TKIP AP to another day.
 
>>>> [185219.617236] eth1: Ext scan results too large (272 bytes).
>> Truncating
>>>> results to 270 bytes.

> I tried increasing the "data" size from 200 to 300 in hermes.h, and the
> message went away.  I was able to associate to D-Link DIR-615 when it
> was set to WPA1.
> 
> I think it should be safe to increase the side of "data" and remove the
> unused "flags" filed at the end.  Let's make "data" 256 bytes to make it a nice
> round number.

Thanks for checking that. I'll set data to 316 bytes. This makes the agere_ext_scan_info 384 (256+128) bytes. That copes with the worst case you saw, and gives a nice alignment to the array of scan structures (total size now a round 24k).

> I'm sorry, I'm going to be offline soon, and I really cannot do any more
> tests.

Thank you for the feedback and testing, not to mention past maintainership of the driver.


Regards,

Dave.


  reply	other threads:[~2008-08-06 18:33 UTC|newest]

Thread overview: 75+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-02 10:14 [PATCH 00/19] orinoco: WPA for Agere based cards kilroyd
2008-08-02 10:14 ` [PATCH 01/19] orinoco: Add ESSID specific scanning for Agere fw kilroyd
2008-08-02 10:14   ` [PATCH 02/19] orinoco: Update scan translation kilroyd
2008-08-02 10:14     ` [PATCH 03/19] orinoco: Specify all three parameters to every Hermes command kilroyd
2008-08-02 10:14       ` [PATCH 04/19] orinoco: Move EXPORT_SYMBOL declarations next to exported function kilroyd
2008-08-02 10:14         ` [PATCH 05/19] orinoco: Add function to execute Hermes initialisation commands synchronously kilroyd
2008-08-02 10:14           ` [PATCH 06/19] orinoco: Move firmware download functionality into new module kilroyd
2008-08-02 10:14             ` [PATCH 07/19] orinoco: Make firmware download logic more generic kilroyd
2008-08-02 10:14               ` [PATCH 08/19] orinoco: Extend hermes_dld routines for Agere firmware kilroyd
2008-08-02 10:14                 ` [PATCH 09/19] orinoco: Invoke firmware download in main driver kilroyd
2008-08-02 10:14                   ` [PATCH 10/19] orinoco: Fix transmit for Agere/Lucent with fw 9.x kilroyd
2008-08-02 10:14                     ` [PATCH 11/19] orinoco: address checkpatch typedef warning kilroyd
2008-08-02 10:14                       ` [PATCH 12/19] orinoco: Use extended Agere scans available on 9.x series firmwares kilroyd
2008-08-02 10:14                         ` [PATCH 13/19] orinoco: Don't use boolean parameter to record encoding type kilroyd
2008-08-02 10:14                           ` [PATCH 14/19] orinoco: Split wevent work thread from wevent sending kilroyd
2008-08-02 10:14                             ` [PATCH 15/19] orinoco: Use a macro to define wireless handlers kilroyd
2008-08-02 10:14                               ` [PATCH 16/19] orinoco: Add WE-18 ioctls for WPA kilroyd
2008-08-02 10:14                                 ` [PATCH 17/19] orinoco: Send association events to userspace kilroyd
2008-08-02 10:14                                   ` [PATCH 18/19] orinoco: Process bulk of receive interrupt in a tasklet kilroyd
2008-08-02 10:14                                     ` [PATCH 19/19] orinoco: Add MIC on TX and check on RX kilroyd
2008-08-02 10:22                               ` [PATCH 15/19] orinoco: Use a macro to define wireless handlers kilroyd
2008-08-04  4:48   ` [PATCH 01/19] orinoco: Add ESSID specific scanning for Agere fw Pavel Roskin
2008-08-04 15:34     ` Dan Williams
2008-08-05 16:22       ` Jean Tourrilhes
2008-09-02 23:06         ` Jean Tourrilhes
2008-09-08 12:48           ` Pavel Roskin
2008-09-08 16:45             ` Jean Tourrilhes
2008-09-08 18:32             ` Jean Tourrilhes
2008-09-09 18:37               ` Dave
2008-09-09 19:33                 ` Jean Tourrilhes
2008-09-09 21:20                   ` Tomas Winkler
2008-09-09 21:44                     ` Jean Tourrilhes
2008-09-13  4:17               ` Pavel Roskin
2008-09-15 21:17                 ` Jean Tourrilhes
2008-08-05 21:15       ` Pavel Roskin
2008-08-05 21:50         ` Dave
2008-08-05 21:55         ` Dan Williams
2008-08-05 22:48           ` Pavel Roskin
2008-08-06 13:13             ` Dan Williams
2008-08-06 13:48               ` Pavel Roskin
2008-08-06 19:26                 ` Dave
2008-08-06 19:29               ` Dave
2008-08-06 20:56                 ` Dan Williams
2008-08-06 21:03                   ` Dan Williams
2008-08-06 21:08                   ` Dave
2008-08-07  2:48                     ` Dan Williams
2008-08-07 18:43                       ` Dave
2008-08-07 19:42                         ` Dan Williams
2008-08-07 20:17                           ` Dave
2008-08-07 20:46                             ` Dan Williams
2008-08-07 21:08                           ` Dave
2008-08-08 14:51                             ` Dan Williams
2008-08-04  3:57 ` [PATCH 00/19] orinoco: WPA for Agere based cards Pavel Roskin
2008-08-04 23:09   ` Dave
2008-08-04 23:28     ` Dan Williams
2008-08-06  0:37       ` Pavel Roskin
2008-08-06 18:33         ` Dave [this message]
2008-08-06 21:01           ` Dan Williams
2008-08-07  8:06             ` Jouni Malinen
2008-08-06 21:28         ` [PATCH 12/19] orinoco: Use extended Agere scans available on 9.x series firmwares kilroyd
2008-08-05 22:38     ` [Orinoco-devel] [PATCH 00/19] orinoco: WPA for Agere based cards Pavel Roskin
2008-08-08  0:02       ` Dave
2008-08-05 22:59     ` Pavel Roskin
2008-08-05 23:46       ` Dave
2008-08-06  0:41         ` [Orinoco-devel] " Pavel Roskin
2008-08-05 22:22   ` [PATCH 07/19] orinoco: Make firmware download logic more generic kilroyd
2008-08-05 22:22     ` [PATCH 09/19] orinoco: Invoke firmware download in main driver kilroyd
2008-08-05 22:22       ` [PATCH 12/19] orinoco: Use extended Agere scans available on 9.x series firmwares kilroyd
2008-08-20 19:28 ` [PATCH 00/19] orinoco: WPA for Agere based cards John W. Linville
2008-08-20 20:49   ` Dave
2008-08-20 21:06     ` Larry Finger
2008-08-20 21:07     ` Johannes Berg
2008-08-20 21:22       ` Johannes Berg
2008-08-20 23:07         ` Dave
2008-08-21  6:42           ` Johannes Berg

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4899EE69.6050205@gmail.com \
    --to=kilroyd@googlemail.com \
    --cc=dcbw@redhat.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=orinoco-devel@lists.sourceforge.net \
    --cc=proski@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).