All of lore.kernel.org
 help / color / mirror / Atom feed
From: Holger Schurig <hs4233@mail.mn-solutions.de>
To: linux-wireless@vger.kernel.org
Subject: Re: mac80211 regression: doesn't associate automatically
Date: Fri, 23 Nov 2007 09:44:40 +0100	[thread overview]
Message-ID: <200711230944.40222.hs4233@mail.mn-solutions.de> (raw)
In-Reply-To: <8e6f94720711221232p16b90daaya5fe3550729b49c8@mail.gmail.com>

> Also, are you sure you understand completely what is going on?

That Debian was not able to set the script might really be a 
different problem.

> As far as I can see, the Debian wireless-tools ifup script
> (package version 29-1) *is* setting the key before it sets the
> essid. In fact, setting the ssid and key both happen in a
> pre-up script, which is run before the interface is even
> brought up.

Yes, Debian /etc/network/if-pre-up.d/wireless-tools first sets 
all stuff up, then calls iwconfig essid, and only then brings 
the interface up.

So you're right, the "doesn't associate" problem is not Debian's 
fault (I actually never suspected Debian to be faulty, it worked 
flawless all the time and I haven't changed anything there).

Now I disabled Debians startup scripts and did the thing 
manually. And voila, it doesn't work when done manually.


As it stands, I now have two sequences that doesn't associate 
with mac80211/b43:


Debian's sequence:

$ pccardctl insert
$ iwconfig eth1 key:11111
$ iwconfig eth1 essid MUMBLEFUTZ
$ ifconfig eth1 up

My older sequence:

$ pccardctl insert
$ ifconfig eth1 up
$ iwconfig eth1 essid MUMBLEFUTZ
$ iwconfig eth1 key:11111




Litte side note: with the first sequence, after about a minute 
the driver scans and associates anyway:

10:27:50.846680   eth1     Set Encryption key:****-****-**
10:27:55.440949   eth1     Set ESSID:"MUMBLEFUTZ"
10:29:06.047881   eth1     Scan request completed
10:29:06.064521   eth1     Custom driver 
event:ASSOCINFO(ReqIEs=...)
10:29:06.064550   eth1     New Access Point/Cell 
address:00:13:19:80:DA:30

While I find the timeout of a minute way too high (especially for 
a moving environment, e.g. storage warehouse), it's better than 
nothing.

The second sequence doesn't associate at all, not even after five 
minutes.


Again, both (!) sequences work with several non-mac80211-drivers 
that I used in production during the last 5 years. And I'm still 
inclined to call this a regression: things that used to work 
stopped working.

  reply	other threads:[~2007-11-23  8:44 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-22  8:12 mac80211 regression: doesn't associate automatically Holger Schurig
2007-11-22 13:05 ` Johannes Berg
2007-11-22 13:26   ` John W. Linville
2007-11-23  0:23     ` Pavel Roskin
     [not found]       ` <47462A72.8010303@wetwork.net>
2007-11-23  1:26         ` Pavel Roskin
2007-11-23  8:06       ` Holger Schurig
2007-11-23  8:22         ` Pavel Roskin
2007-11-23  9:03           ` Holger Schurig
2007-11-26 15:34             ` Dan Williams
2007-11-22 14:14   ` Holger Schurig
2007-11-22 14:41     ` Johannes Berg
2007-11-22 15:05       ` Holger Schurig
2007-11-22 15:13         ` Johannes Berg
2007-11-22 15:43           ` Holger Schurig
2007-11-22 15:41         ` Johannes Berg
2007-11-22 15:46           ` Johannes Berg
2007-11-22 15:58             ` Holger Schurig
2007-11-23 12:15               ` Johannes Berg
2007-11-22 16:19           ` Holger Schurig
2007-11-22 20:32             ` Will Dyson
2007-11-23  8:44               ` Holger Schurig [this message]
2007-11-23 12:48               ` Johannes Berg
2007-11-23 19:34                 ` Will Dyson
2007-11-23 20:22                   ` Johannes Berg
2007-11-23 12:46             ` Johannes Berg
2007-11-23 13:23               ` Holger Schurig
2007-11-24 21:36                 ` Johannes Berg
2007-11-24 22:39                   ` Will Dyson
2007-11-25 10:53                     ` Johannes Berg
2007-11-26  7:27                       ` Holger Schurig
2007-11-22 15:45     ` Holger Schurig

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=200711230944.40222.hs4233@mail.mn-solutions.de \
    --to=hs4233@mail.mn-solutions.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.