Linux wireless drivers development
 help / color / mirror / Atom feed
From: Giacomo Comes <comes@naic.edu>
To: Dave Kilroy <kilroyd@googlemail.com>
Cc: Giacomo Comes <comes@naic.edu>, linux-wireless@vger.kernel.org
Subject: Re: orinoco_cs module and WPA not working
Date: Fri, 3 Dec 2010 23:36:46 -0400	[thread overview]
Message-ID: <20101204033646.GA22662@monopoli.naic.edu> (raw)
In-Reply-To: <AANLkTi=qvZ-Uj1T=9Xc8LyyxKvgNw4CKV8Zx2fDfo4uH@mail.gmail.com>

On Fri, Dec 03, 2010 at 10:49:55PM +0000, Dave Kilroy wrote:
> >> >> But after removing the line: ap_scan=2
> >> >> the association fails.
> >> >> The log is in the second attachment.
> >> >>
> >> >> Also I have included in the 3rd attachement wpa_supplicant.log when
> >> >> NetworkManager is used.
> >>
> >> > The failure and NM case are the same. There is still a problem with
> >> > scanning. wpa_supplicant initiates a scan, and it appears to time out.
> >> > Without scan results wpa_supplicant is not able to select an
> >> > appropriate AP.
> >> >
> >> > Is the driver reporting any scanning issues in dmesg while
> >> > wpa_supplicant is running?
> >
> > In dmesg there is:
> > ADDRCONF(NETDEV_UP): eth1: link is not ready
> >
> > and on standard error:
> > ioctl[SIOCSIWENCODEEXT]: Invalid argument
> 
> Those are expected.
> 
> I'm at a loss. I've looked at the wpa_supplicant code, and had another
> look at the driver. The scan should be a plain wildcard scan - which
> you've identified works.
> 
> Does setting scan_ssid=1 in the wpa_supplicant network block change
> the behaviour? That's usually only necessary for hidden SSIDs - but
> I'd like to know if the scan succeeds in this case.

No It doesn't work.
But I have more informations for you.

I have been testing different versions of wpa_supplicant
and I have found that if a use wpa_supplicant 0.7.0 or earlier,
it works. With 0.7.1 or newer it fails.
wpa_supplicant 0.7.0 works even without applying your patch.

I hope this helps.
Giacomo

  reply	other threads:[~2010-12-04  3:36 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-22  2:42 orinoco_cs module and WPA not working Giacomo Comes
2010-11-24 19:06 ` Dave Kilroy
2010-11-25  1:45   ` Giacomo Comes
     [not found]     ` <AANLkTi=nkayyyzECi6MO87ZO-CUpZeNP007_hMp8LiPV@mail.gmail.com>
     [not found]       ` <20101126040742.GA5238@monopoli.naic.edu>
2010-11-28 16:10         ` Dave Kilroy
2010-11-30  2:19           ` Giacomo Comes
2010-12-01 21:52             ` Dave Kilroy
2010-12-02  0:22               ` Giacomo Comes
2010-12-02 17:46                 ` Dave Kilroy
2010-12-03  0:10                   ` Giacomo Comes
     [not found]                     ` <AANLkTinLaa+dOiq67DAt+KYfnxUEkNgWEiE2x1NtT9RE@mail.gmail.com>
2010-12-03 17:29                       ` Dave Kilroy
2010-12-03 20:23                         ` Giacomo Comes
2010-12-03 22:49                           ` Dave Kilroy
2010-12-04  3:36                             ` Giacomo Comes [this message]
2010-12-04 12:01                               ` Dave Kilroy
2010-12-04 13:47                                 ` Giacomo Comes
2010-12-04 14:40                                   ` Dave Kilroy
2010-12-06  4:28                                     ` Giacomo Comes
2010-12-06 18:43                                       ` Dave Kilroy
2010-12-06 21:25                                         ` Giacomo Comes
2010-12-08 19:24                                           ` Dave Kilroy
2010-12-09  2:58                                             ` Giacomo Comes

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=20101204033646.GA22662@monopoli.naic.edu \
    --to=comes@naic.edu \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@vger.kernel.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