Figure out better way to manage bat0 (batman-adv devices/interfaces) via networkmanager #2
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As an rls maintainer, I want things to be managed via standard management utilities, so if i create a network device/interface (such as bat0), it should be managed by the default network management tool in FCOS (which happens to be https://networkmanager.dev)
As of right now there is no
batman-adv
configuration settings for networkmanager ( https://networkmanager.dev/docs/api/latest/ref-settings.html ).Sidenote: systemd-networkd supports
batman-adv
, however fedora coreos does not support systemd-networkd by default. to solve, we might be able to fiddle with this by layering the systemd-extra package on top of our image. 🤷this discussion seems to indicate that layering systemd-networkd is now supported better (https://github.com/coreos/fedora-coreos-config/pull/574)
This may also cause some consideration for using flatcar linux? 🤔 (flatcar sticks with old coreos systemd manages everything, whereas fcos uses things that have best support from upstream fedora stuff)maybe not, flatcar uses docker, fcos uses podman. podman is the 🐐use networkmanager dispatcher https://gist.github.com/frafra/4952d8d1795b5732366c
ref: https://networkmanager.dev/docs/api/latest/NetworkManager-dispatcher.html
potentially solved in
7361d4143f
pending testing#14