From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Zhongliang Zhao <zhao@iam.unibe.ch>
Cc: linux-wireless@vger.kernel.org
Subject: Re: iw dev wlan0 link - "Not connected"
Date: Wed, 28 Jul 2010 10:30:21 -0700 [thread overview]
Message-ID: <AANLkTindXiF6pjzSgz7Gp_w7qy1EeOqNgq8safE00FvG@mail.gmail.com> (raw)
In-Reply-To: <4C500460.5000505@iam.unibe.ch>
On Wed, Jul 28, 2010 at 3:20 AM, Zhongliang Zhao <zhao@iam.unibe.ch> wrote:
> On 07/26/2010 07:23 PM, Luis R. Rodriguez wrote:
>>
>> On Mon, Jul 26, 2010 at 2:29 AM, Zhongliang Zhao<zhao@iam.unibe.ch>
>> wrote:
>>
>>>
>>> Dear all,
>>>
>>> When I use "iw dev wlan0 link" to get information on wlan0 (basically to
>>> check the channel used on wlan0),
>>> it says: " Not connected "
>>>
>>> Can someone tell me how to fix this?
>>>
>>
>> Refer to:
>>
>> http://wireless.kernel.org/en/users/Documentation/iw#Getting_link_status
>>
>> And then:
>>
>>
>> http://wireless.kernel.org/en/users/Documentation/iw#Establishing_a_basic_connection
>>
>> What you really want to use is:
>>
>> http://wireless.kernel.org/en/users/Documentation/wpa_supplicant
>>
>> Luis
>>
>
>
> Luis, thanks for the reply. But actually we're working on mesh nodes with
> the iw-tool installed, so maybe we should use the "mesh" interface mode. In
> this case, how to solve the problem?
http://wireless.kernel.org/en/users/Documentation/iw#Creating_and_inspecting_Mesh_Point_interfaces_with_iw
Note for ath9k you currently have to issue a scan to kick the card to
beacon, its a bug, not dealt with yet.
Luis
prev parent reply other threads:[~2010-07-28 18:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-26 9:29 iw dev wlan0 link - "Not connected" Zhongliang Zhao
2010-07-26 17:23 ` Luis R. Rodriguez
2010-07-28 10:20 ` Zhongliang Zhao
2010-07-28 17:30 ` Luis R. Rodriguez [this message]
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=AANLkTindXiF6pjzSgz7Gp_w7qy1EeOqNgq8safE00FvG@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=zhao@iam.unibe.ch \
/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).