From: Christian Lamparter <chunkeey@googlemail.com>
To: "David H. Lynch Jr." <dhlii@dlasys.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: CARL9170 features
Date: Mon, 24 May 2010 23:40:06 +0200 [thread overview]
Message-ID: <201005242340.06728.chunkeey@googlemail.com> (raw)
In-Reply-To: <4BFAECC0.2000007@dlasys.net>
On Monday 24 May 2010 23:16:48 David H. Lynch Jr. wrote:
> I am trying to kick carl9170 1.0.9 into either add-hoc or monitor
> mode or anything else where I can xmit to any wireless device. I do not
> care if the receiving device is interested - so long as the radio ACK's
> the packet, which it should do automatically.
iwconfig and all other wext-based wireless-tools are obsolete.
The new CLI "iw" can be found on:
http://wireless.kernel.org/en/users/Documentation/iw
> I tried iwconfig wl_ath mode ad-hoc
> And I get and errror:
>
> root# iwconfig wl_ath mode ad-hoc
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wl_ath ; Device or resource busy.
This is expected. The wl_ath interface must be *down* before
you can chance the operation mode of the master interface.
try: (of course, after calling: ifconfig wl_ath down)
iw dev wlanX ibss join <SSID> freq/channel <MHz/Chan No.>
> root# iwconfig wl_ath mode monitor
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wl_ath ; Device or resource busy.
iw dev wlanX set monitor [otherbss control ...]
> root# iwconfig wl_ath mode master
> Error for wireless request "Set Mode" (8B06) :
> SET failed on device wl_ath ; Invalid argument.
Master/Accesspoint mode is no longer fully implemented into the
kernel and therefore needs a userspace daemon: hostapd.
http://wireless.kernel.org/en/users/Documentation/hostapd
> I can add something to the driver if needed if you could recommend
> another wireless driver for a reference.
Well, we could add a beacon scheduler. This way we might be able
to support more than just one AP/IBSS interface. But this is
really complicated as the whole CAB implementation needs to be
extended to support multiple (concurrent) AP/IBSS links.
(And of course, there's the problem of the shared TSF in such a
configuration, so this might not be feasible after all...)
Regards,
Chr
prev parent reply other threads:[~2010-05-24 21:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 21:16 CARL9170 features David H. Lynch Jr.
2010-05-24 21:31 ` Gábor Stefanik
2010-05-24 21:40 ` Christian Lamparter [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=201005242340.06728.chunkeey@googlemail.com \
--to=chunkeey@googlemail.com \
--cc=dhlii@dlasys.net \
--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).