From: Dan Williams <dcbw@redhat.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Mohamed Abbas <mabbas@linux.intel.com>,
Jouni Malinen <jkm@devicescape.com>,
netdev@vger.kernel.org, jbenc@suse.cz
Subject: Re: [PATCH 5/7] d80211: indicate if unassociate/radio off status
Date: Wed, 30 Aug 2006 09:41:43 -0400 [thread overview]
Message-ID: <1156945303.2725.7.camel@localhost.localdomain> (raw)
In-Reply-To: <200608291601.56901.flamingice@sourmilk.net>
On Tue, 2006-08-29 at 16:01 -0700, Michael Wu wrote:
> On Tuesday 29 August 2006 15:50, Michael Wu wrote:
> > On Tuesday 29 August 2006 15:28, Mohamed Abbas wrote:
> > > SIOCGIWAP will always report the bssid no
> > > matter what the status of our link.
> >
> > That is not the case at the moment. Were you planning to change that?
> >
> Opps, it looks like it is the case. Ignore that.
>
> Perhaps we should make SIOCGIWAP always reflect the AP we're currently
> associated to, and 00:00:00:00:00:00 if there is none.
>
> -Michael Wu
Um, that's how it's supposed to work, and that's how it's always worked.
If you're associated with an access point, its BSSID is returned from
SIOCGIWAP. If you are not associated, 00:00:00:00:00:00 is returned.
Please don't break that. The driver should also send the appropriate
netlink IWAP events when it gets disconnected or when a successful
connection occurs using wireless_send_event().
If a valid BSSID is returned from an SIOCGIWAP, it's assumed that that
access point will allow your traffic to pass, i.e. all required
association and authentication has successfully completed.
SIOCGIWAP behavior does _not_ necessarily reflect what BSSID is set with
SIOCSIWAP.
Dan
next prev parent reply other threads:[~2006-08-30 13:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 20:49 [PATCH 5/7] d80211: indicate if unassociate/radio off status mabbas
2006-08-28 21:17 ` Michael Wu
2006-08-29 17:55 ` Jouni Malinen
2006-08-29 22:28 ` Mohamed Abbas
2006-08-29 22:50 ` Michael Wu
2006-08-29 23:01 ` Michael Wu
2006-08-30 13:41 ` Dan Williams [this message]
2006-08-30 17:22 ` Michael Wu
2006-09-21 17:01 ` Jiri Benc
2006-09-21 19:03 ` Dan Williams
2006-09-21 19:47 ` mabbas
2006-09-21 20:30 ` Dan Williams
2006-09-21 20:39 ` mabbas
2006-09-21 22:38 ` Jiri Benc
2006-09-21 22:55 ` Jean Tourrilhes
2006-09-22 0:42 ` Jouni Malinen
2006-09-22 0:57 ` Jean Tourrilhes
2006-09-22 22:29 ` [d80211 patch 1/1] setting bss freq and phymode using rx_status mabbas
2006-09-25 16:16 ` Jiri Benc
2006-09-25 17:15 ` mabbas
2006-09-27 15:34 ` Jiri Benc
2006-09-22 8:32 ` [PATCH 5/7] d80211: indicate if unassociate/radio off status Johannes Berg
2006-09-22 14:05 ` Dan Williams
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=1156945303.2725.7.camel@localhost.localdomain \
--to=dcbw@redhat.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=jkm@devicescape.com \
--cc=mabbas@linux.intel.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).