=== chris14_ is now known as chris14
=== shokohsc51086 is now known as shokohsc5108
[15:27] <v0lZy> hi
[15:27] <v0lZy> I am having some issues with netplan and network manager
[15:28] <v0lZy> I have 2 devices, an openvswitch bridge called vswitch0 and enp2s0 which attaches to it. I have netplan configured to bring enp2s0 up with NetworkManager, but with disabled dhcp and no IP settings... literally i just need the link to be up
[15:28] <v0lZy> I bring vswitch0 up with networkd as renderer
[15:28] <v0lZy> Currently, when i do nmcli dev, I see all devices as unmanaged
[15:28] <v0lZy> but i should be seeing enp2s0 managed , right?
[15:29] <v0lZy> Overall, the problem is that cockpit requires networkmanager to manage something, else it doesnt show updates cause it thinks its offline.
[15:34] <sdeziel> v0lZy: if you ask `netplan` to use `networkd` then `nmcli` won't see them as managed by NetworkManager because they are managed by `systemd-networkd`. So it looks normal, unless I misunderstood something
[15:35] <v0lZy> sdeziel: I think you are misunderstanding
[15:35] <sdeziel> v0lZy: that could very well be
[15:36] <v0lZy> I have an openvswitch (which debian doesn't include in NetworkManager) bridge, that I assign an IP to. The enp2s0 is connected to that bridge, but should not have an IP.
[15:36] <v0lZy> because of the Debian version of NetworkManager being unable to manage openvswitch bridges, I have 2 files in netplan; 00-enp2s0-no-ip.yaml and 10-vswitch0-dhcpv4.yaml
[15:37] <v0lZy> i used 'networkd' as rendere for 00-enp2s0-no-ip.yaml, and 'NetworkManager' for 10-vswitch0-dhcpv4.yaml
[15:37] <v0lZy> currently, I'm connected to the system... ip add show correctly shows an IP obtained via DHCP on vswitch0, and no ip on enp2s0 with link state 'up'
[15:38] <v0lZy> however, if i do 'nmcli dev'
[15:38] <v0lZy> I get a list of devices on my system, all of which are unmanged
[15:38] <v0lZy> enp2s0 shows up as 'unmanaged' ... even though i have a file telling netplan to manage it via NetworkManager
[15:39] <v0lZy> if i check /run/systemd/network ... I see the configuration that I'm intending to use, but thing is I'm using cockpit and it has a dependency on NetworkManager showing some interface that its managing to be up, to grab updates
[15:40] <v0lZy> So In essence, I would like to have enp2s0 managed by NetworkManager, but not have an IP assigned to it
[15:55] <v0lZy> I am assuming what I'm IdeaS?
[15:55] <v0lZy> bah
[15:55] <v0lZy> typo
[15:55] <v0lZy> what i meant
[15:55] <v0lZy> is if anyone has any ideas?
[15:56] <sdeziel> v0lZy: `nmcli` is a NetworkManager tool so it isn't aware of anything managed by `systemd-networkd`
[16:00] <v0lZy> thats logical
[16:01] <v0lZy> it shows what NetworkManager is managing
[16:01] <v0lZy> my problem is that it doesn't show that its managing enp2s0
[16:01] <v0lZy> even though netplan has renderer: NetworkManager in the enp2s0 file and the actual configuration IS applied.
[16:02] <v0lZy> this is my yaml file:
[16:02] <v0lZy> network:
[16:02] <v0lZy>   version: 2
[16:02] <v0lZy>   renderer: NetworkManager
[16:02] <v0lZy>   ethernets:
[16:02] <v0lZy>     enp2s0:
[16:02] <v0lZy>       dhcp4: no
[16:02] <v0lZy>       dhcp6: no
[16:13] <sdeziel> v0lZy: I am not sure you can have some devices managed by `networkd` and some other by `NetworkManager` but maybe wrong. Is netplan complaining?
[16:14] <v0lZy> its not complaining
[16:14] <v0lZy> of course you can have that
[16:14] <sdeziel> v0lZy: TIL
[16:15] <v0lZy> TIL?
[16:15] <v0lZy> whats that stand for?
[16:15] <v0lZy> on the of course you can have that part; networkmanager just creates config files. Is all it does.
[16:16] <v0lZy> And ok, maybe issues commands to bring them up/down
[16:16] <v0lZy> but essentially, its not interfacing with the tcp/ip stack or anything, thats not its job
[16:16] <v0lZy> hence if you configure that at some level on other interfaces its not configuring, it shouldnt be an issue
[16:16] <sdeziel> v0lZy: TIL stands for "Today I Learned"
[16:17] <v0lZy> Ah, OK
[16:20] <sdeziel> v0lZy: it seems that Ubuntu's NetworkManager supports openvswitch (at least `nmcli conn add type ovs-bridge conn.interface bridge0` did something here on 22.04) so maybe that's something for you to test?
[16:21] <v0lZy> I can add openvswitch
[16:21] <v0lZy> but you can't do much with it
[16:21] <v0lZy> it understands that there is sucha  thing as an openvswitch device
[16:21] <v0lZy> but theres no module for it in ubuntu so you cant manage it
=== shokohsc51082 is now known as shokohsc5108