All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Roth <joelz@pobox.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Joel Roth <joelz@pobox.com>, Bob Copeland <me@bobcopeland.com>,
	linux-wireless@vger.kernel.org
Subject: Re: ath5k and Atheros AR242x - No scan results
Date: Thu, 16 Jul 2009 00:07:43 -1000	[thread overview]
Message-ID: <20090716100743.GC3867@sprite> (raw)
In-Reply-To: <1247734019.19467.0.camel@johannes.local>

On Thu, Jul 16, 2009 at 10:46:59AM +0200, Johannes Berg wrote:
> On Wed, 2009-07-15 at 20:14 -1000, Joel Roth wrote:
> 
> > # iwlist wlan0 ap
> > 
> > wlan0     Interface doesn't have a list of Peers/Access-Points
> 
> # iwlist wlan0 scan
> 
> should have worked, but I'm glad you're making good use of iw :)

Hmm. It does work _now_, provided the interface is UP.

That may be thanks to having a recent kernel with the latest
compat-wireless drivers.

I was also misled by assuming iwlist's 'ap' option would
provide useful information. 

To summarize what I now know, the steps to follow for basic
wireless connectivity to an unencrypted network would be:

1. kernel and driver setup - use compat-wireless

2. set wireless interface to UP

	ifconfig <interface> up

3. find available networks using

	iw dev <interface> scan
 or 
	iwlist <interface> scan

4. connect to a network using 

	iw dev <interface> connect <SSID> 

5. acquire IP address, typically by

	dhclient <interface>

Regards,

Joel
 
> johannes



-- 
Joel Roth

  reply	other threads:[~2009-07-16 10:13 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30 17:09 ath5k and Atheros AR242x - No scan results Joel Roth
2009-06-30 17:52 ` Luis R. Rodriguez
2009-06-30 18:25   ` Joel Roth
2009-06-30 18:34     ` Luis R. Rodriguez
2009-06-30 21:16 ` Nick Kossifidis
2009-07-01  7:24   ` Joel Roth
2009-07-04 19:10     ` Joel Roth
2009-07-12 11:23 ` Joel Roth
2009-07-12 15:08   ` Nick Kossifidis
2009-07-12 20:34     ` Joel Roth
2009-07-13 14:08       ` Bob Copeland
2009-07-14  6:54         ` Joel Roth
2009-07-16  6:14           ` Joel Roth
2009-07-16  6:54             ` Joel Roth
2009-07-16  8:46             ` Johannes Berg
2009-07-16 10:07               ` Joel Roth [this message]
2009-07-16 10:13                 ` Johannes Berg
2009-07-17  6:06                 ` Holger Schurig
2009-07-17  8:18                   ` Johannes Berg

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=20090716100743.GC3867@sprite \
    --to=joelz@pobox.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=me@bobcopeland.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.