Version: (using KDE 4.4.3) Compiler: gcc-4.4.3 OS: Linux Installed from: Gentoo Packages If I add the BSSID from my accesspoint to the Network Configuration (instead of __:__:__:__:__:__), there is no way to get connection working. It seems as if knetworkmanager is not even trying to connect to. I have to add all BSSIDs because of the problem, I have to deal with many different APs that have the same name (SSID).
I can confirm this on kde 4.5 rc2 (using the fedora prerelease-packages) and with the networkmanagement plasmoid. Additionally once a network connection has been created with an bssid, it's no longer possible to remove that bssid without deleting the connection.
knetworkmanager provides BSSID in a bad format to NM daemon, which causes connection failures. Also, MAC address is not sent correctly when you use "Restrict to Interface" combo. For WiFi that causes connection failure, for wired the setting is just ignored. (in reply to comment #1) > Additionally once a network connection has been created with an bssid, > it's no longer possible to remove that bssid without deleting the connection. Thats's corrected by the patch. As a temporary solution, it's possible to manually edit the connection in ~/.kde/share/apps/networkmanagement/connections/<connection_UUID> and set bssid empty: bssid= All these problems are fixed by the attached patch.
Created attachment 51638 [details] fix BSSID and MAC address provided to NM
marking confirmed(new), I'll whip up some test builds incorporating the patch.
I can confirm this on KDE 4.6. Has the patch already been commited?
It has not been committed.
fwiw, all current fedora kde-plasma-networkmanagement packages do include this patch now.
Thank you for the patch! Works fine on gentoo (self patched)
Patch submitted to reviewboard, for wider exposure, https://git.reviewboard.kde.org/r/100674/
Patch accepted, committed, http://quickgit.kde.org/?p=networkmanagement.git&a=commit&h=e6a2b8626c998f5ebc2e6bf0bf927462201e039d