From: Ivo van Doorn <ivdoorn@gmail.com>
To: Michael Wu <flamingice@sourmilk.net>
Cc: netdev@vger.kernel.org, Olivier <o.cornu@gmail.com>,
Jiri Benc <jbenc@suse.cz>
Subject: Re: Dscape ieee80211: enabling/disabling the radio
Date: Wed, 10 May 2006 15:37:11 +0200 [thread overview]
Message-ID: <200605101537.15213.IvDoorn@gmail.com> (raw)
In-Reply-To: <200605091836.10138.flamingice@sourmilk.net>
[-- Attachment #1: Type: text/plain, Size: 2157 bytes --]
On Wednesday 10 May 2006 00:36, Michael Wu wrote:
> On Tuesday 09 May 2006 18:01, Ivo van Doorn wrote:
> > A user on the forums Olivier Cornu (added to the CC list) has done some
> > investigation into the scanning behaviour of the dscape stack.
> > Basicly the dscape stack is performing active scanning while the device is
> > down, but during the active scan it is sending packets out, or at least
> > attempting to do so. Besides the question if active scanning is preferred
> > over passive scanning while interface is down, active scanning fails
> > because the packets that should be send are being send through the regular
> > xmit routines of the interface. (IFF_UP is not set for the interface)
> >
> > This means that besides enabling the radio which should be done in the
> > driver, the stack should either bring up the interface when doing an active
> > scan, or resort to passive scanning while interface is down.
> >
> If you can passive scan while the interface is down, I don't think it's really
> down. In adm8211, nothing can be sent or received when the interface is down.
> The radio is always off when the interface is down. Taking the interface up
> just for a scan and then taking it back down doesn't sound too good either. I
> think scans should be prohibited while the interface is down, since leaving
> the interface on isn't gonna do anything bad unless you put in the info to
> associate.
True, I agree here. But when rt2x00 was using the ipw stack a much
requested feature from users was to be able to perform scanning while
interface was down. (The requests did not specify if it they wanted passive or active scanning)
But the reason for these requests was that some user space applications and/or
distribution network scripts relied on the fact that the driver was capable of scanning
while the interface was down, so the interface would only be brought up at boot time,
when there was no desired AP in the scan result.
I don't know which distributions or user space application these were, but due to the amount
of these requests it had been considered an important feature.
Ivo
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-05-10 13:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 12:00 Dscape ieee80211: enabling/disabling the radio Ivo van Doorn
2006-05-09 22:01 ` Ivo van Doorn
2006-05-09 22:36 ` Michael Wu
2006-05-10 5:29 ` Olivier
2006-05-10 13:37 ` Ivo van Doorn [this message]
2006-05-10 13:55 ` Jiri Benc
2006-05-10 10:52 ` Jiri Benc
2006-05-10 13:55 ` Ivo van Doorn
2006-05-10 10:42 ` Jiri Benc
2006-05-10 13:53 ` Ivo van Doorn
2006-05-10 14:10 ` Jiri Benc
2006-05-10 17:03 ` Jouni Malinen
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=200605101537.15213.IvDoorn@gmail.com \
--to=ivdoorn@gmail.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.cornu@gmail.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;
as well as URLs for NNTP newsgroup(s).