| Line 1: | Line 1: | ||
== WPA supplicant? == | == WPA supplicant? == | ||
Q: Will this work for (wireless) connections needing wpa_supplicant (for WPA(2)/WPA Enterprise) as well? --[[User:Fkooman|Fkooman]] 07:59, 14 May 2009 (UTC) | Q: Will this work for (wireless) connections needing wpa_supplicant (for WPA(2)/WPA Enterprise) as well? --[[User:Fkooman|Fkooman]] 07:59, 14 May 2009 (UTC) | ||
Especially for WPA Enterpise that uses EAP-GTC? [http://bugzilla.gnome.org/show_bug.cgi?id=451027 #451027 Add GTC phase2 support] --[[User:Maxious|Maxious]] 15:24, 3 June 2009 (UTC) | |||
== /etc/sysconfig/network-scripts vs. keyfile == | == /etc/sysconfig/network-scripts vs. keyfile == | ||
Q: Why not use the keyfile plugin by default? If we stay with /etc/sysconfig/network-scripts settings files, will NM use all the same options that the existing network-scripts use, and if any new options need to be defined, will the network-scripts ifup/ifdown be updated to support them too? I think that the most advantageous way forward will be to make sure all NM settings are 100% network-scripts-compatible so you can switch back and forth between NM and the "network" service without having to reconfigure network settings in two different locations, or having to modify the settings to be compatible. If that isn't going to be the case, then perhaps using keyfile makes more sense, completely divorcing yourself of any illusion that NM is compatible with the network-scripts. I'd rather see the former case than the latter, but it may not be feasible to have 100% network-scripts compatibility. | Q: Why not use the keyfile plugin by default? If we stay with /etc/sysconfig/network-scripts settings files, will NM use all the same options that the existing network-scripts use, and if any new options need to be defined, will the network-scripts ifup/ifdown be updated to support them too? I think that the most advantageous way forward will be to make sure all NM settings are 100% network-scripts-compatible so you can switch back and forth between NM and the "network" service without having to reconfigure network settings in two different locations, or having to modify the settings to be compatible. If that isn't going to be the case, then perhaps using keyfile makes more sense, completely divorcing yourself of any illusion that NM is compatible with the network-scripts. I'd rather see the former case than the latter, but it may not be feasible to have 100% network-scripts compatibility. | ||
--[[User:Cra|Cra]] 12:52, 16 May 2009 (UTC) | --[[User:Cra|Cra]] 12:52, 16 May 2009 (UTC) | ||
Revision as of 15:24, 3 June 2009
WPA supplicant?
Q: Will this work for (wireless) connections needing wpa_supplicant (for WPA(2)/WPA Enterprise) as well? --Fkooman 07:59, 14 May 2009 (UTC)
Especially for WPA Enterpise that uses EAP-GTC? #451027 Add GTC phase2 support --Maxious 15:24, 3 June 2009 (UTC)
/etc/sysconfig/network-scripts vs. keyfile
Q: Why not use the keyfile plugin by default? If we stay with /etc/sysconfig/network-scripts settings files, will NM use all the same options that the existing network-scripts use, and if any new options need to be defined, will the network-scripts ifup/ifdown be updated to support them too? I think that the most advantageous way forward will be to make sure all NM settings are 100% network-scripts-compatible so you can switch back and forth between NM and the "network" service without having to reconfigure network settings in two different locations, or having to modify the settings to be compatible. If that isn't going to be the case, then perhaps using keyfile makes more sense, completely divorcing yourself of any illusion that NM is compatible with the network-scripts. I'd rather see the former case than the latter, but it may not be feasible to have 100% network-scripts compatibility. --Cra 12:52, 16 May 2009 (UTC)