All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
	645055@bugs.debian.org, "Antoine Beaupré" <anarcat@koumbit.org>
Subject: Re: Bug#645055: realtek 8188CE ad-hoc mode not supported
Date: Wed, 12 Oct 2011 21:10:30 -0500	[thread overview]
Message-ID: <4E964896.5050004@lwfinger.net> (raw)
In-Reply-To: <1318461858.4024.197.camel@deadeye>

On 10/12/2011 06:24 PM, Ben Hutchings wrote:
> 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)?

I don't think that implementation of the WEXT interface is necessary. As to 
using iw, the following sequence worked:

iw dev wlan14 interface add wlan15 type adhoc
iw dev  set rename5 type managed
iw dev  set rename5 type adhoc

Why it was called "rename5" when I asked for "wlan15" is not understood, but the 
iw interface changes the mode for an existing interface when using rtl8192ce.

BTW, I added a new iface because I did not want to interrupt my internat connection.

Larry

  parent reply	other threads:[~2011-10-13  2:10 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       ` Bug#645055: realtek 8188CE ad-hoc mode not supported Ben Hutchings
2011-10-13  1:46         ` Antoine Beaupré
2011-10-13  2:10         ` Larry Finger [this message]
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=4E964896.5050004@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=645055@bugs.debian.org \
    --cc=anarcat@koumbit.org \
    --cc=ben@decadent.org.uk \
    --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 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.