From: Dan Williams <dcbw@redhat.com>
To: Helge Hafting <helgehaf@mail.aitel.hist.no>
Cc: linux-wireless@vger.kernel.org
Subject: Re: reproducible association with wrong essid, iwl3945
Date: Mon, 10 Mar 2008 10:53:21 -0400 [thread overview]
Message-ID: <1205160801.3347.35.camel@localhost.localdomain> (raw)
In-Reply-To: <47D508A5.6090805@mail.aitel.hist.no>
On Mon, 2008-03-10 at 11:08 +0100, Helge Hafting wrote:
> Get a normal association so the network works. (WEP encryption)
> $ iwconfig wlan0 nonexistent_essid key s:correct_key
>
> The network keeps working! I would expect the driver to look
> for an access point with the different essid, and fail
> if no such access point exists.
> Two different networks with the same encryption string is possible,
> after all.
Should definitely fail, disassociate, and send the SIOCSIWAP event with
00:00:00:00:00:00 via wireless_send_event().
Dan
next prev parent reply other threads:[~2008-03-10 14:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-10 10:08 reproducible association with wrong essid, iwl3945 Helge Hafting
2008-03-10 14:53 ` Dan Williams [this message]
2008-03-10 20:49 ` Helge Hafting
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=1205160801.3347.35.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=helgehaf@mail.aitel.hist.no \
--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