GNOME Bugzilla – Bug 654772
Create New Wireless Network should not default to WEP
Last modified: 2020-11-12 14:31:08 UTC
Click the Create New Wireless Network button. The wireless security field defaults to "WEP 128-bit Passphrase." Instead, it should default to "WPA & WPA2 Personal."
Unfortunately at this point most recent kernels do not work correctly with WPA Ad-Hoc mode, so the default to WEP is currently correct. Future kernel fixes should allow this to work better, and we'll be implementing mini AP mode for those drivers that support it.
How can I check that the driver supports WPA-encrypted hotspot? Where can I track the status of this problem?
I think this is fixed now. At least in KDE, both WPA and AP mode is working.
Well, WEP seems to still be the default Maybe now WPA should be default and AP mode be enabled by default.
I'm looking into this one.
Please add a dependency on bug #734589.
Created attachment 283172 [details] [review] Patch to change the default for shared connections supporting AP mode The attached patch should solve this issue after bug #734589 is solved.
(In reply to comment #7) > Created an attachment (id=283172) [details] [review] > Patch to change the default for shared connections supporting AP mode > > The attached patch should solve this issue after bug #734589 is solved. Looks right to me (I did test it however, no device support)
Review of attachment 283172 [details] [review]: ::: src/libnm-gtk/nm-wifi-dialog.c @@ +870,3 @@ } } else if (is_adhoc) { + if (dev_caps & NM_WIFI_DEVICE_CAP_AP) I think this be NM_WIFI_DEVICE_CAP_RSN... The driver can more easily support AdHoc RSN/WPA2 than it can real AP mode, and we should assume if the driver advertises support for RSN that it can do AdHoc RSN.
Created attachment 334985 [details] [review] libnma/wifi-dialog: default wifi security to WPA2 for new shared networks (bgo #654772) [thaller@redhat.com: modified original patch to check for CAP_RSN and libnma change]
The combo never contains the "WPA2" choice for ad-hoc networks because of: case NMU_SEC_WPA2_PSK: if (adhoc) return FALSE; /* FIXME: Kernel WPA Ad-Hoc support is buggy */ in nm_utils_security_valid(), and so there is no point in selecting it as default (this also has the negative effect that the first entry "None" is selected instead of WEP).
Probably we should enable WPA/WPA2 for ad-hoc networks before merging this patch. Dan, the comment in nm_utils_security_valid() says that kernel WPA ad-hoc support is buggy, is that still the case with recent kernels or things have improved?
The issue is actually with WPA1 adhoc. I think WPA2/RSN adhoc is OK, but not as many drivers supported WPA2 adhoc at the time. WPA1 adhoc will probably never be fixed, as the recommendation is to use WPA2/RSN adhoc instead.
bugzilla.gnome.org is being shut down in favor of a GitLab instance. We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time. If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/ Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).