hi, i’d like to whip up a tumbleweed vm or 2 (in kvm). is there an easy way to configure static ip via simple files? perhaps by installing the likes of either netplan or systemd-networkd i suppose, tho if there’s a more native tumbleweed way i’d be happy to use it.
is it sensible to remove NetworkManager packages (which ones?), or wiser to just disable and ignore them, or is it truly best to use nmcli?
A bare bones vm with a strong (tumbleweed) foundation, preferably the most minimal set of packages, on which i can deploy ceph, or nagios, or backuppc, or, with vnc, a crm, or gnucash, or a browser.
Does it work to remove NetworkManager packages or are they too entangled with dependencies to even bother trying?
And what is the native tumbleweed flavor of static ip configuration? Preferably not yast, chef, puppet, vagrant, docker, libvirt, kde systemsettings, or networkmanager, preferably just the bare native skeleton method?
bor@tw:~> sudo zypper rm NetworkManager
Reading installed packages...
Resolving package dependencies...
The following 13 packages are going to be REMOVED:
NetworkManager NetworkManager-bluetooth NetworkManager-branding-openSUSE
NetworkManager-openvpn NetworkManager-openvpn-gnome NetworkManager-pptp
NetworkManager-pptp-gnome NetworkManager-tui NetworkManager-vpnc
13 packages to remove.
After the operation, 7.8 MiB will be freed.
Continue? [y/n/v/...? shows all options] (y):
And what is the native tumbleweed flavor of static ip configuration?
Define “native”. Default network management is NetworkManager. YaST supports NetworkManager and wicked. If you are not interested in YaST you can use whatever you like.
preferably just the bare native skeleton method?
If the only requirement is configuration files - NetworkManager stores configuration in simple ini files which can be prepared with any text editor.
Well i installed the MicroOS .iso into a kvm guest with static ip and was surprised it came up neither resolving dns nor routing out through our gateway. Also disappointed it defaults to selinux. The tumbleweed packaging seems to be working rather better for me. Tho microos provides good insight what packages i may choose to trim.
Now thisis what i was looking for. Surprised it didn’t fix the microos networking problems tho, even after a reboot.
Bridged. Two internal networks, one of which has a gateway to the internet. i simply installed two guests by feeding the Tumbleweed and MicroOS ISOs to virt-install and gave the installers our network info. Since the Tumbleweed guest seems to work better i tried just plugging the Tumbleweed /etc/NetworkManager/system-connections/enp* into the MicroOS guest and rebooting it but that didn’t help. it feels reminiscent of selinux issues and i confess that turns me right off, happy that Tumbleweed defaults to apparmor.
If you fire up virt-manager and edit the guest and add a new network interface and select bridge and add your bro or br1, then apply and boot does a second interface come up on the machine with appropriate address etc?
i asked chatgpt if dnsmasq is capable to set a static ip for the host on which it runs, it answered yes and gave details, in summary add “address=/myhostname/192.168.1.2” to the config. i think it’s mistaken but i confess i’m not certain, anyone?