From: Ben Hutchings <ben@decadent.org.uk>
To: "Larry Finger" <Larry.Finger@lwfinger.net>,
"Antoine Beaupré" <anarcat@koumbit.org>
Cc: linux-wireless <linux-wireless@vger.kernel.org>, 645055@bugs.debian.org
Subject: Re: Bug#645055: realtek 8188CE ad-hoc mode not supported
Date: Thu, 13 Oct 2011 03:25:17 +0100 [thread overview]
Message-ID: <1318472723.4024.208.camel@deadeye> (raw)
In-Reply-To: <4E964896.5050004@lwfinger.net>
[-- Attachment #1: Type: text/plain, Size: 1557 bytes --]
On Wed, 2011-10-12 at 21:10 -0500, Larry Finger wrote:
> 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.
The change_interface operation appears to be used in implementation of
nl80211 too.
> 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,
udev's persistent name generator isn't able to distinguish the two
interfaces by MAC address, so it decides the new interface should also
be named 'wlan14'. udev does renaming in two steps for some reason, and
the second step obviously fails.
> 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.
Hmm. Maybe the change_interface operation is only needed to change
type/mode while the interface is up.
Antoine, did you bring the interface down before setting its mode?
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 --]
next prev parent reply other threads:[~2011-10-13 2:25 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
2011-10-13 2:25 ` Ben Hutchings [this message]
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=1318472723.4024.208.camel@deadeye \
--to=ben@decadent.org.uk \
--cc=645055@bugs.debian.org \
--cc=Larry.Finger@lwfinger.net \
--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