linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Alexey Fisher <bug-track@fisher-privat.net>
Cc: Kernel Testers List <kernel-testers@vger.kernel.org>,
	linux-wireless@vger.kernel.org
Subject: Re: why differnet wlan drivers need different settings?
Date: Sat, 25 Oct 2008 13:03:34 +0200	[thread overview]
Message-ID: <200810251303.35295.rjw@sisk.pl> (raw)
In-Reply-To: <200810251153.25533.bug-track@fisher-privat.net>

On Saturday, 25 of October 2008, Alexey Fisher wrote:
> May be this is the wrong plase to ask. 

Yeah, better ask that on linux-wireless@vger.kernel.org (CCed).

> The question is: Why differnet wlan drivers use different settings to stay 
> silent - powered on but not trying to associate to any accespoint?
> For example: ipw2200 - if wlan was connfigured like:
> 
> iwconfig wlan1 essid "my-ap" chan 6 ap my:aps:mac ?key s:pass
> 
> this will normaly connect to my secure ?AP. and if i set after this:
> ?
> iwconfig wlan1 essid off ap off
> 
> it will connect to unsecure AP of my neighbour or of Dr.Evil :)
> to disable association on ipw2200 i need to set all this and plus "chan 0".
> With this cnowleg i want to set up iwl3945, and surprise it's not working. 
> This driver do not accepted "chan 0" and instead of "essid off" it did 
> "essid """
> 
> Are there any unified way to keep adapter powered on but not trying to 
> associate to some AP?
> 

       reply	other threads:[~2008-10-25 10:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200810251153.25533.bug-track@fisher-privat.net>
2008-10-25 11:03 ` Rafael J. Wysocki [this message]
2008-10-25 13:55   ` why differnet wlan drivers need different settings? John W. Linville
2008-10-25 20:45     ` Alexey Fisher
2008-10-27 16:13       ` Dan Williams
2008-11-03 21:25         ` Dan Williams
2008-11-03 22:28           ` Alexey Fisher

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=200810251303.35295.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --cc=bug-track@fisher-privat.net \
    --cc=kernel-testers@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).