From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org, Jouni Malinen <j@w1.fi>,
Reinette Chatre <reinette.chatre@intel.com>
Subject: Re: Problem with IEEE80211_MONITORING_INTERVAL
Date: Wed, 22 Apr 2009 13:56:18 +0100 [thread overview]
Message-ID: <1240404978.3378.4.camel@localhost.localdomain> (raw)
In-Reply-To: <1240402497.21978.12.camel@johannes.local>
Hi Johannes,
> > > > I just don't see anything in the kernel that would ever set the
> > > > interface down, as indicated there.
> >
> > so I have installed the latest wireless-testing kernel now.
> >
> > CTRL-EVENT-SCAN-RESULTS
> > Trying to authenticate with 00:1f:f3:fa:58:59 (SSID='HON Circle' freq=2452 MHz)
> > Trying to associate with 00:1f:f3:fa:58:59 (SSID='HON Circle' freq=2452 MHz)
> > Could not read SSID from driver.
> > WPA: No SSID info found (msg 1 of 4).
> > Associated with 00:1f:f3:fa:58:59
> > WPA: Key negotiation completed with 00:1f:f3:fa:58:59 [PTK=CCMP GTK=CCMP]
> > CTRL-EVENT-CONNECTED - Connection to 00:1f:f3:fa:58:59 completed (auth) [id=1 id_str=]
> >
> > <starting dhclient wlan0 now>
> >
> > CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
> > l2_packet_receive - recvfrom: Network is down
>
> I still don't understand this. Is the AP disconnecting you? Are you
> running NM on the side?
I am not running NM. Just plain wpa_supplicant and dhclient. However I
do have a suspicion that this is faulty firmware on my card and that
this messes things up. I had been doing testing with WiMAX and I run
into some issues and was speculating about interoperability. I started
testing with unreleased firmware. That would indeed explain why I don't
see this kind of issues with any other dongle I attached to the laptop.
I will reboot into a kernel that uses the official firmware.
Regards
Marcel
next prev parent reply other threads:[~2009-04-22 12:56 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-15 23:21 Problem with IEEE80211_MONITORING_INTERVAL Marcel Holtmann
2009-04-16 0:21 ` Johannes Berg
2009-04-16 0:44 ` Johannes Berg
2009-04-16 1:12 ` Marcel Holtmann
2009-04-16 1:08 ` Marcel Holtmann
2009-04-16 1:16 ` Johannes Berg
2009-04-16 6:14 ` Kalle Valo
2009-04-16 9:12 ` Johannes Berg
2009-04-16 9:43 ` Johannes Berg
2009-04-16 9:49 ` Kalle Valo
2009-04-16 9:58 ` Johannes Berg
2009-04-16 9:59 ` Kalle Valo
2009-04-16 10:04 ` Johannes Berg
2009-04-16 10:08 ` Kalle Valo
2009-04-16 10:18 ` Johannes Berg
2009-04-16 10:23 ` Kalle Valo
2009-04-16 9:46 ` Johannes Berg
2009-04-20 17:13 ` Marcel Holtmann
2009-04-20 17:20 ` Johannes Berg
2009-04-20 17:26 ` Marcel Holtmann
2009-04-20 17:32 ` Johannes Berg
2009-04-21 19:56 ` Marcel Holtmann
2009-04-21 21:19 ` Johannes Berg
2009-04-22 7:32 ` Marcel Holtmann
2009-04-22 9:03 ` Johannes Berg
2009-04-22 9:12 ` Marcel Holtmann
2009-04-22 9:45 ` Johannes Berg
2009-04-22 11:17 ` Marcel Holtmann
2009-04-22 11:53 ` Marcel Holtmann
2009-04-22 12:14 ` Johannes Berg
2009-04-22 12:56 ` Marcel Holtmann [this message]
2009-04-22 13:27 ` John W. Linville
2009-04-22 17:35 ` reinette chatre
2009-04-22 5:04 ` Kalle Valo
2009-04-22 7:27 ` Marcel Holtmann
2009-04-20 18:29 ` Jouni Malinen
2009-04-21 10:47 ` Marcel Holtmann
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=1240404978.3378.4.camel@localhost.localdomain \
--to=marcel@holtmann.org \
--cc=j@w1.fi \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=reinette.chatre@intel.com \
/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