netplan does not configure interfaces with different renderers

[Vladimir Sokolovsky]

DPU: BlueField
OS: Ubuntu 20.04
netplan.io-0.103-0ubuntu5~20.04.1

We want to manage some of the network interfaces using NetworkManager and other with networkd:

# ls /etc/netplan/
55-mlnx.yaml 60-mlnx.yaml

# cat /etc/netplan/55-mlnx.yaml
network:
  version: 2
  ethernets:
    tmfifo_net0:
      renderer: NetworkManager
      dhcp4: false
      addresses:
        - 192.168.100.2/30
      nameservers:
        addresses: [ 192.168.100.1 ]
      routes:
      - to: 0.0.0.0/0
        via: 192.168.100.1
        metric: 1025
    oob_net0:
      renderer: NetworkManager
      dhcp4: true

# cat /etc/netplan/60-mlnx.yaml
network:
  version: 2
  ethernets:
    enp3s0f0s0:
      renderer: networkd
      dhcp4: 'true'
    enp3s0f1s0:
      renderer: networkd
      dhcp4: 'true'

With the configuration above netplan does not set IP address for tmfifo_net0 interface:

# ifconfig tmfifo_net0
tmfifo_net0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
        ether 00:1a:ca:ff:ff:05 txqueuelen 1000 (Ethernet)
        RX packets 102 bytes 10337 (10.3 KB)
        RX errors 0 dropped 0 overruns 0 frame 0
        TX packets 60 bytes 7873 (7.8 KB)
        TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[Lukas Märdian (slyon)]

Hi, the configuration is looking correct as far as I can tell.

Could you please show the output of the following two commands, to see what NetworkManager is doing there?

$ nmcli con show | grep netplan
$ nmcli con show netplan-tmfifo_net0

[Vladimir Sokolovsky (vlad-a)]

# nmcli con show | grep netplan
netplan-oob_net0 aa93b667-6aac-3804-91e9-4958e07fdb2f ethernet --
netplan-tmfifo_net0 77742971-069b-34fa-9761-413eb2bd29a4 ethernet --

# nmcli con show netplan-tmfifo_net0
connection.id: netplan-tmfifo_net0
connection.uuid: 77742971-069b-34fa-9761-413eb2bd29a4
connection.stable-id: --
connection.type: 802-3-ethernet
connection.interface-name: tmfifo_net0
connection.autoconnect: yes
connection.autoconnect-priority: 0
connection.autoconnect-retries: -1 (default)
connection.multi-connect: 0 (default)
connection.auth-retries: -1
connection.timestamp: 1631086654
connection.read-only: no
connection.permissions: --
connection.zone: --
connection.master: --
connection.slave-type: --
connection.autoconnect-slaves: -1 (default)
connection.secondaries: --
connection.gateway-ping-timeout: 0
connection.metered: unknown
connection.lldp: default
connection.mdns: -1 (default)
connection.llmnr: -1 (default)
connection.wait-device-timeout: -1
802-3-ethernet.port: --
802-3-ethernet.speed: 0
802-3-ethernet.duplex: --
802-3-ethernet.auto-negotiate: no
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: auto
802-3-ethernet.s390-subchannels: --
802-3-ethernet.s390-nettype: --
802-3-ethernet.s390-options: --
802-3-ethernet.wake-on-lan: --
802-3-ethernet.wake-on-lan-password: --
ipv4.method: manual
ipv4.dns: 192.168.100.1
ipv4.dns-search: --
ipv4.dns-options: --
ipv4.dns-priority: 0
ipv4.addresses: 192.168.100.2/30
ipv4.gateway: --
ipv4.routes: { ip = 0.0.0.0/0, nh = 192.168.100.1, m>
ipv4.route-metric: -1
ipv4.route-table: 0 (unspec)
ipv4.routing-rules: --
ipv4.ignore-auto-routes: no
ipv4.ignore-auto-dns: no
ipv4.dhcp-client-id: --
ipv4.dhcp-iaid: --
ipv4.dhcp-timeout: 0 (default)
ipv4.dhcp-send-hostname: yes
ipv4.dhcp-hostname: --
ipv4.dhcp-fqdn: --
ipv4.dhcp-hostname-flags: 0x0 (none)
ipv4.never-default: no
ipv4.may-fail: yes
ipv4.dad-timeout: -1 (default)
ipv6.method: ignore
ipv6.dns: --
ipv6.dns-search: ...

[Lukas Märdian (slyon)]

Thank you. It looks like the connection settings are correctly detected by NetworkManager, but for some reason it does not bring up the connection.

Could you please check the output of the following command to see how the tmfifo_net0 interface is being used?

$ nmcli dev

You could also try to "nmcli con up netplan-tmfifo_net0" to check how NetworkManager reacts to that.