Beniamino Galvani
Beniamino Galvani
Hi, when NM runs in initrd, it saves its state in `/run/NetworkManager`. After switch root, the new NM instance reads the content of that directory (which includes initrd-generated connection profiles...
> IAFAIU, this is is caused about configuration NOT propagating the other way. F.e. when 'generating' the connections in the initrd, interfaces which were supposed to be disabled are re-enabled,...
> For `keep-configuration=no` to make sense, you probably anyway need to configure the real-root. It's not that you could boot an machine the first time and it's gonna work (is...
Makes sense to me, ifcfg support is also being deprecated in NetworkManager and will be removed eventually.
@erig0 we got another report of this issue in NetworkManager : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1521. Which nft rules should NM add? I see above you suggested: ``` table inet wg-mark { chain mangle...
``` client = NM.Client.new(None) ``` creates a new client object by connecting to NM via D-Bus. The error "Could not connect" comes from Glib gsocketclient.c and indicates that the connection...
As far as I remember, the actor is supposed to be run after NM (which depends on D-Bus) and so it seems unexpected that the D-Bus socket is missing at...