| [09:46] <Nadhi> Hi Chan | |
| [09:47] <Nadhi> one query how to specify name of connection in netplan. The format in network manager is nmcli c m <uuid> connection.id <id_name> | |
| [09:52] <slyon> Hi Nadhi, you can specify the name of the connection via the connection handle itself, e.g.: networks -> ethernets -> YOUR_CONNECTION_NAME -> dhcp4: true | |
| [09:53] <slyon> In this case you would most probably also need a match condition to select the corresponding interface, e.g.: networks -> ethernets -> YOUR_CONNECTOIN_NAME -> match -> name: eth0 | |
| [09:53] <slyon> NetworkManager will then pickup the name as "netplan-YOUR_CONNECTION_NAME" | |
| [10:00] <Nadhi> how to set a custom name instead of netplan-CONNECTION_NAME? My use case is network manager should set some custom name like "xyz" | |
| [10:03] <slyon> The "netplan-" prefix is hardcoded by netplan currently. And there is no easy way to change this, AFAIK | |
| [10:05] <Nadhi> okay, Thanks for the info slyon. | |
| [10:10] <Nadhi> @sylon How to activate/deactivate a connection? nmcli c up <uuid> / nmcli c down <uuid> | |
| [10:11] <Nadhi> any attribute in YAML which does that? | |
| [10:14] <slyon> yw! Netplan only prepares the configuration for your. It does not handle runtime modifications (like up/down). By default all defined connections/interfaces are brought up on "netplan apply" (or reboot). If you want to apply up/down at runtime you could you "nmcli", as you suggested | |
| [10:14] <slyon> *you could use | |
| [10:21] <Nadhi> Also, for a connection created by interface why these fields are empty | |
| [10:21] <Nadhi> 802-3-ethernet.mac-address:802-3-ethernet.cloned-mac-address:802-3-ethernet.generate-mac-address-mask:802-3-ethernet.mac-address-blacklist:802-3-ethernet.mtu:auto802-3-ethernet.s390-subchannels:802-3-ethernet.s390-nettype:802-3-ethernet.s390-options:basically, output of nmcli -t c s <uuid> | |
| [10:22] <Nadhi> type error: connection created by netplan* | |
| [10:24] <slyon> Those settings are related to the match.macaddress and CONNECTION.macaddress settings in the YAML, did you set them there? Would you mind pasing your netplan config? | |
| [10:29] <Nadhi> network: version: 2 renderer: NetworkManager ethernets: enc2a80: addresses: - 11.2.1.99/24 s2: match: name: enc2d40 dhcp4: yes | |
| [10:30] <Nadhi> I m concerned about these 2 values 802-3-ethernet.s390-subchannels: and 802-3-ethernet.s390-nettype | |
| [10:30] <Nadhi> basically getting subchannels and driver type | |
| [10:30] <Nadhi> which works for nmcli created devices | |
| [10:32] <slyon> Okay, so you do not set any macaddress or MTU related settings in YAML, that explains why they are empty for you. wrt. s390-* settings: those are unfortunately not supported by netplan at this time | |
| [10:32] <Nadhi> okay slyon, Thanks for the info.. | |