Bug#645055: realtek 8188CE ad-hoc mode not supported
A message that is not in the archive (sent off-list or not yet received): 20111012052940.17383.59248.reportbug@localhost
A message that is not in the archive (sent off-list or not yet received): 1318424918.4024.180.camel@deadeye
A message that is not in the archive (sent off-list or not yet received): [email protected]
A message that is not in the archive (sent off-list or not yet received): [email protected]
Quoted 14 lines · Ben Hutchings
Quoted 5 lines · Antoine Beaupré
Quoted 4 lines · Ben Hutchings
Can you create an ad-hoc interface like this:
iw dev wlan0 interface add wlan1 type adhoc
Quoted 7 lines
Quoted 1 line
(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?
Quoted 6 lines
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.
Signature · 2 lines
Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
Quoted 6 lines · Ben Hutchings
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_interfaceoperation)?
Seems to me really counter-intuitive that it didn't work. It was the first time I ever see such a problem.
I have seen numerous drivers not support "Master" or "Monitor" mode, because of limitations of the implementation or the hardware, but if this is purely a API problem, it seems like a problem that should be fixed...
Is this the right place though?
A.
Signature · 4 lines
The idea that Bill Gates has appeared like a knight in shining armour to lead all customers out of a mire of technological chaos neatly ignores the fact that it was he who, by peddling second-rate technology, led them into it in the first place. - Douglas Adams (1952-2001)
Quoted 6 lines · Ben Hutchings
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_interfaceoperation)?
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
Quoted 9 lines · Larry Finger
Quoted 6 lines · Ben Hutchings
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_interfaceoperation)?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.
Quoted 7 lines
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 adhocWhy 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.
Quoted 5 lines
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.
Signature · 2 lines
Ben Hutchings Quantity is no substitute for quality, but it's the only one we've got.
Quoted 10 lines · Ben Hutchings
Quoted 5 lines
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_interfaceoperation is only needed to change type/mode while the interface is up.Antoine, did you bring the interface down before setting its mode?
Crap. No, I didn't. And now it works if I bring it down first. Oh well, I guess I just made a lot of noise for nothing, this bug can be closed, thank you!
A.
Signature · 1 line
Travail, du latin Tri Palium trois pieux, instrument de torture.