summaryrefslogtreecommitdiff
path: root/libnm-util/nm-setting-vlan.c
diff options
context:
space:
mode:
authorDan Winship <danw@gnome.org>2013-09-09 09:40:40 -0400
committerDan Winship <danw@gnome.org>2013-09-12 18:34:23 -0400
commit066b59224192131fe5aefcf27491e283e9b7e0c3 (patch)
tree90467e9590f41b5adad002d86b0883c44802a251 /libnm-util/nm-setting-vlan.c
parent2688ae4950070f2a57db1347d9ebfbce0898fe53 (diff)
downloadNetworkManager-066b59224192131fe5aefcf27491e283e9b7e0c3.tar.gz
all: standardize on NMSettingWired:mac-address for all VLANs
Currently, ethernet-based VLANs can specify the hardware address of the parent device (and, in theory, the cloned hardware address and MTU of the VLAN device) by using an NMSettingWired in addition to the NMSettingVlan. The theory was that non-ethernet-based VLANs, when we eventually supported them, would likewise use the setting type corresponding to their parent device. However, this turns out to be both complicated (the settings plugins and connection editor would have a hard-to-impossible time figuring out which setting type to use in some cases) and incorrect (for most L2 settings [eg, BSSID, bond mode, etc], the VLAN can't have its own values separate from the parent device). What we should have done was just have :mac-address, :cloned-mac-address, and :mtu properties on NMSettingVlan. However, at this point, for backward-compatibility, we will just stick with using a combination of NMSettingVlan and NMSettingWired, but we will use NMSettingWired regardless of the underlying hardware type.
Diffstat (limited to 'libnm-util/nm-setting-vlan.c')
-rw-r--r--libnm-util/nm-setting-vlan.c16
1 files changed, 7 insertions, 9 deletions
diff --git a/libnm-util/nm-setting-vlan.c b/libnm-util/nm-setting-vlan.c
index 72b623bac5..256e16fa22 100644
--- a/libnm-util/nm-setting-vlan.c
+++ b/libnm-util/nm-setting-vlan.c
@@ -681,8 +681,8 @@ nm_setting_vlan_class_init (NMSettingVlanClass *setting_class)
* If given, specifies the kernel name of the VLAN interface. If not given,
* a default name will be constructed from the interface described by the
* parent interface and the #NMSettingVlan:id , ex 'eth2.1'. The parent
- * interface may be given by the #NMSettingVlan:parent property or by a
- * hardware address property, eg #NMSettingWired:mac-address.
+ * interface may be given by the #NMSettingVlan:parent property or by the
+ * #NMSettingWired:mac-address property of an #NMSettingWired.
**/
g_object_class_install_property
(object_class, PROP_IFACE_NAME,
@@ -693,9 +693,8 @@ nm_setting_vlan_class_init (NMSettingVlanClass *setting_class)
"constructed from the interface described by the "
"parent interface and the 'id' property, ex "
"'eth2.1'. The parent interface may be given by "
- "the 'parent' property or by a hardware address "
- "property, eg the 'wired' settings' 'mac-address' "
- "property.",
+ "the 'parent' property or by the 'mac-address' "
+ "property of a 'wired' setting.",
NULL,
G_PARAM_READWRITE | G_PARAM_CONSTRUCT | NM_SETTING_PARAM_SERIALIZE));
@@ -704,8 +703,8 @@ nm_setting_vlan_class_init (NMSettingVlanClass *setting_class)
*
* If given, specifies the parent interface name or parent connection UUID
* from which this VLAN interface should be created. If this property is
- * not specified, the connection must contain a hardware address in a
- * hardware-specific setting, like #NMSettingWired:mac-address.
+ * not specified, the connection must contain a #NMSettingWired:mac-address
+ * in an #NMSettingWired setting.
**/
g_object_class_install_property
(object_class, PROP_PARENT,
@@ -715,8 +714,7 @@ nm_setting_vlan_class_init (NMSettingVlanClass *setting_class)
"parent connection UUID from which this VLAN "
"interface should be created. If this property is "
"not specified, the connection must contain a "
- "hardware address in a hardware-specific setting, "
- "like the 'wired' settings' 'mac-address' property.",
+ "'wired' setting with a 'mac-address' property.",
NULL,
G_PARAM_READWRITE | G_PARAM_CONSTRUCT | NM_SETTING_PARAM_SERIALIZE));