Created attachment 661672 [details] iw phy output Description of problem: When using gnome network tool to create a hotspot it only creates an ad-hoc wifi hotspo and not the real AP hotspot as advertised available in F18. Version-Release number of selected component (if applicable): NetworkManager-1:0.9.7.0-9.git20121004.fc18 network-manager-applet-0.9.7-4.git20121016.fc18 How reproducible: Always Steps to Reproduce: 1. Open up gnome network tool 2. Set up a wifi hotspot 3. Check the wifi hotspot created Actual results: Ad-hoc wifi hotspot is created. Expected results: AP hotspot should be created. Additional info: Ath9k should have the possibility to trigger the AP mode, driver and wifi card are compatible. iw phy output added.
Could you attach /var/log/messages from when NM activates the hotspot connection. And the output of $ nmcli con list id "the name of the hotspot connection"
Created attachment 663726 [details] /var/log/messages Same bug with Linksys WUSB54GC adapter Attached: /var/log/messages iw list: Supported interface modes: * IBSS * managed * AP * AP/VLAN * WDS * monitor * mesh point software interface modes (can always be added): * AP/VLAN * monitor
Created attachment 664339 [details] /var/log/messages
Created attachment 664340 [details] nmcli con list id "Hotspot" ouput Here are the two files requested.
Same bug in KDE BZ: https://bugs.kde.org/show_bug.cgi?id=311705
Still no progress with latest update. Always using Ad-hoc mode even if Ath9k driver supports AP mode.
Real AP mode requires support from the GUI tools to create set "AP mode" if the device supports it. I did some patches a while back for real AP mode for the GNOME control-center network panel, but those are not yet in the version of the control center that F18 ships. NetworkManager core daemon supports real AP hotspot, but I guess we need some updates for the UI tools too.
Could you provide here a documentation on how-to implement this feature in GUI? requested by: https://bugs.kde.org/show_bug.cgi?id=311705#c5
Patch was merged in Gnome, could it be backported to F18 ? (Waiting on next Gnome release seems to be long and as it seems not being too invasive, it should be backported). This feature could be very useful to many Android users out there.
The support was added upstream for GNOME 3.8 (it's available in the Fedora 19 tree), and there are no plans to backport it to Fedora 18. There's a GNOME Fedora 19 test day tomorrow, with images for testing: https://lists.fedoraproject.org/pipermail/test-announce/2013-March/000625.html
Why are there no plans to backport this to fedora 18, when the core part is already present in, and only GUI modifications are required? Could it be called the pinnacle of stupidity to advertise a feature as a "game changer" as I saw somewhere in the run-up to f18, and then not actually deliver it, without actually notifying anyone of this rather egregious omission? Why is it necessary for a user to waste a day of his time searching for solutions to the hotspot not working before stumbling over a random bugzilla entry? This is not "CLOSED" until it is made clear that F18 does not actually support the advertised feature, so people shouldn't waste their time looking! It sounds as if KDE in F18 might actually support this before the "standard" desktop.
Scratch that. KDE already supports it. This does not reflect well on the coordinatedness of the fedora team...
I tried to get it working on F19 Alpha today, and it still doesn't work as expected, so no, it's not fixed. Version-Release number of selected component (if applicable): NetworkManager-1:0.9.8.1-1.git20130327.fc19 network-manager-applet-0.9.8.1-1.git20130327.fc19
Created attachment 739295 [details] nmcli con list id "Hotspot" ouput on F19
Created attachment 739297 [details] /var/log/messages
Fixed on latest update from F19. NetworkManager-1:0.9.8.1-1.git20130327.fc19 network-manager-applet-0.9.8.1-3.git20130430.fc19
(In reply to Martin Holec from comment #8) > Could you provide here a documentation on how-to implement this feature in > GUI? > > requested by: https://bugs.kde.org/show_bug.cgi?id=311705#c5