Linux wireless drivers development
 help / color / mirror / Atom feed
From: Ben Hutchings <ben@decadent.org.uk>
To: linux-wireless <linux-wireless@vger.kernel.org>
Cc: 645055@bugs.debian.org, "Antoine Beaupré" <anarcat@koumbit.org>
Subject: Re: Bug#645055: realtek 8188CE ad-hoc mode not supported
Date: Thu, 13 Oct 2011 00:24:12 +0100	[thread overview]
Message-ID: <1318461858.4024.197.camel@deadeye> (raw)
In-Reply-To: <20111012160135.GK3366@decadent.org.uk>

[-- Attachment #1: Type: text/plain, Size: 1352 bytes --]

On Wed, 2011-10-12 at 17:01 +0100, Ben Hutchings wrote:
> On Wed, Oct 12, 2011 at 11:20:31AM -0400, Antoine Beaupré wrote:
> > On Wed, 12 Oct 2011 14:08:32 +0100, Ben Hutchings <ben@decadent.org.uk> wrote:
> > > Can you create an ad-hoc interface like this:
> > > 
> > >     iw dev wlan0 interface add wlan1 type adhoc
> > > 
> > > (you'll need the iw package).
> > 
> > Interesting - this works. Didn't know of the iw tool. But this creates a
> > separate interface, kind of odd!
> > 
> > The adhoc mode works like that. I am not sure I understand why it
> > doesn't work with iwconfig, can you enlighten me?
> 
> iwconfig uses the original WEXT (wireless extensions) configuration
> interface.  This interface was never very well specified and was
> implemented in inconsistent ways by different drivers.
> 
> The newer configuration interface used by iw, Network Manager and
> other tools is nl80211 (netlink for IEEE 802.11).
[...]

I looked a little further and saw that nl80211 does support changing
interface type (mode).  But this driver (rtl8192ce) only supports
creating new interfaces, not changing their type.

Should mac80211 drivers generally support changing interface type
(change_interface operation)?

Ben.

-- 
Ben Hutchings
Quantity is no substitute for quality, but it's the only one we've got.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

       reply	other threads:[~2011-10-12 23:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20111012052940.17383.59248.reportbug@localhost>
     [not found] ` <1318424918.4024.180.camel@deadeye>
     [not found]   ` <87pqi2s0cg.fsf@marcos.anarcat.ath.cx>
     [not found]     ` <20111012160135.GK3366@decadent.org.uk>
2011-10-12 23:24       ` Ben Hutchings [this message]
2011-10-13  1:46         ` Bug#645055: realtek 8188CE ad-hoc mode not supported Antoine Beaupré
2011-10-13  2:10         ` Larry Finger
2011-10-13  2:25           ` Ben Hutchings
2011-10-13  2:31             ` Antoine Beaupré

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=1318461858.4024.197.camel@deadeye \
    --to=ben@decadent.org.uk \
    --cc=645055@bugs.debian.org \
    --cc=anarcat@koumbit.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