From: Bob Copeland <me@bobcopeland.com>
To: "Philip A. Prindeville" <philipp_subx@redfish-solutions.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Using compat-wireless w/ 2.6.27.26
Date: Sun, 19 Jul 2009 16:31:50 -0400 [thread overview]
Message-ID: <20090719203150.GA9972@hash.localnet> (raw)
In-Reply-To: <4A635E04.4050204@redfish-solutions.com>
On Sun, Jul 19, 2009 at 10:55:16AM -0700, Philip A. Prindeville wrote:
> Bob Copeland wrote:
> > On Fri, Jul 17, 2009 at 9:27 PM, Philip A.
> >> + iw dev wlan0 interface add ap0 type managed
> >> + ip link set ap0 up
> >> + iw dev ap0 connect xxxx
> >> command failed: Operation not supported (-95)
> >
> > Why are you adding another interface? Should be able to use "iw dev wlan0..."
>
> Because I might want to run two access points (two SSIDs, anyway) on the same
> radio... one with WEP on one VLAN (for Wifi SIP handsets), and one with
> WPA-PSK2 on another VLAN (for laptops, etc).
Hmm, I don't know if it matters, but you were creating it as a managed
interface. Anyway I don't believe ath5k supports that yet - ath9k might.
Someone on ath5k-devel was porting the ath9k virtual wiphy stuff to
ath5k but I haven't heard anything recently.
> But, if you think there's still a doubt, what to look for in the modinfo?
If it says "depends: mac80211,cfg80211,ath" then it is probably the right
one. It just sounds like this bug:
http://bugzilla.kernel.org/show_bug.cgi?id=12315
The fix was merged after 2.6.30, IIRC, but it should definitely be in
compat-wireless. Also check your modules directory for an old ath5k.ko
sitting in drivers/.../wireless/ath5k. It should now be in ath/ath5k.
HTH!
--
Bob Copeland %% www.bobcopeland.com
next prev parent reply other threads:[~2009-07-19 20:32 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 1:27 Using compat-wireless w/ 2.6.27.26 Philip A. Prindeville
2009-07-19 8:58 ` Philip A. Prindeville
2009-07-19 13:38 ` Bob Copeland
2009-07-19 17:55 ` Philip A. Prindeville
2009-07-19 20:31 ` Bob Copeland [this message]
2009-07-20 3:05 ` Philip A. Prindeville
2009-07-20 11:52 ` Bob Copeland
2009-07-20 19:16 ` Philip A. Prindeville
2009-07-20 19:47 ` Luis R. Rodriguez
2009-07-20 23:52 ` Philip A. Prindeville
2009-07-21 20:10 ` Philip A. Prindeville
2009-07-21 23:24 ` Luis R. Rodriguez
2009-07-22 3:28 ` Bob Copeland
2009-07-23 11:24 ` Bob Copeland
2009-07-23 11:59 ` Bob Copeland
2009-07-23 20:29 ` Philip A. Prindeville
2009-07-23 20:33 ` Bob Copeland
2009-07-23 21:53 ` Philip A. Prindeville
2009-07-23 22:21 ` Bob Copeland
2009-07-23 22:45 ` Philip A. Prindeville
2009-07-24 13:58 ` Bob Copeland
2009-07-30 4:36 ` Philip A. Prindeville
2009-07-21 23:26 ` Luis R. Rodriguez
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=20090719203150.GA9972@hash.localnet \
--to=me@bobcopeland.com \
--cc=linux-wireless@vger.kernel.org \
--cc=philipp_subx@redfish-solutions.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).