Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 420807 - net-misc/networkmanager-0.9.4.0-r2 should set channel 1 before trying ad-hoc
Summary: net-misc/networkmanager-0.9.4.0-r2 should set channel 1 before trying ad-hoc
Status: RESOLVED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Linux Gnome Desktop Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-12 10:21 UTC by haarp
Modified: 2013-06-16 18:00 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description haarp 2012-06-12 10:21:09 UTC
On my IWL1000 wireless card, ad-hoc mode can only be entered when the channel is set to 1. When the card was connected to an AP with channel !=1, and then attempts to enter ad-hoc, this will happen:

# iwconfig wlan0 mode ad-hoc
Error for wireless request "Set Mode" (8B06) :
    SET failed on device wlan0 ; Operation not supported.

and the connection will fail.

However, this works:
# iwconfig wlan0 channel 1
# iwconfig wlan0 mode ad-hoc

NetworkManager should set the channel itself prior to setting the mode to ad-hoc, to guarantee proper operation.

also see: https://forums.gentoo.org/viewtopic-t-925380.html
Comment 1 Pavel Šimerda (pavlix) 2012-11-23 07:45:38 UTC
> However, this works:
> # iwconfig wlan0 channel 1
> # iwconfig wlan0 mode ad-hoc
> 
> NetworkManager should set the channel itself prior to setting the mode to
> ad-hoc, to guarantee proper operation.

If you want to know whether NetworkManager is the right place to do that,
and get it fixed, please file bug to the upstream bugzilla. NetworkManager
uses bugzilla.gnome.org.
Comment 2 Pacho Ramos gentoo-dev 2013-06-16 11:58:32 UTC
If still valid with 0.9.8.2, please report to upstream and post link here -> bugzilla.gnome.org
Comment 3 haarp 2013-06-16 18:00:31 UTC
I am not sure if it is still relevant, as I do not have an IWL1000 anymore. My 5300 doesn't seem to have this problem. NEEDINFO is probably the best status, I think.