From: ian <ischram@telenet.be>
To: Andy Green <andy@warmcat.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iwlwifi 3945: secondary interface disallows association
Date: Sun, 08 Jul 2007 22:02:20 +0200 [thread overview]
Message-ID: <469142CC.1000903@telenet.be> (raw)
In-Reply-To: <4691310E.8070406@warmcat.com>
I don't appear to have the same problem with:
-latest version of iwlwifi (0.0.35)
- gentoo-sources-2.6.20 kernel (patched with a relatively old mac80211 package)
I believe fedora has 0.0.24 of iwlwifi embedded?
So the problem might have been fixed already.
Writing this email, after executing your command, when associated on a wpa2
network.
Ian.
Andy Green wrote:
> Hi folks -
>
> I have pretty decent functionality on the 3945abg laptop with the Fedora
> development kernel version of iwlwifi and WPA via wpa_supplicant.
> Connections can stay up over a couple of days or more when I am staying
> close to the AP.
>
> However if I perform this action:
>
> echo -n mon0 > /sys/class/ieee80211/phy0/add_iface
>
> I immediately lose association and cannot reacquire it until I remove
> the iwl3945 module and insert again. I don't have to do anything with
> the new interface, just create it. I tried setting the channel and mode
> of it, but that didn't help with reacquiring an association.
>
> In contrast I can bring up other virtual interfaces okay on, eg, zd1211
> without losing an existing association to the same WPA network.
>
> -Andy
> -
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
>
next prev parent reply other threads:[~2007-07-08 20:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 18:46 iwlwifi 3945: secondary interface disallows association Andy Green
2007-07-08 20:02 ` ian [this message]
2007-07-08 20:32 ` Andy Green
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=469142CC.1000903@telenet.be \
--to=ischram@telenet.be \
--cc=andy@warmcat.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 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.