MicroOS: Configure static network IP via combustion?

**mrmazda** · 22-Mar-2022, 11:15

Static IP can be simple enough, on TW & Leap at least:

Code:

# cat /etc/systemd/network/eth0.network
[Match]
Name=eth0

[Network]
Address=192.168.###.###/24
DNS=192.168.###.##X 1.1.1.1 1.0.0.1
Gateway=192.168.###.##X
IPv6AcceptRA=no
LinkLocalAddressing=no
# systemctl status wickedd
● wickedd.service
     Loaded: masked (Reason: Unit wickedd.service is masked.)
     Active: inactive (dead)
# rpm -qa | grep workManag
# systemctl list-unit-files | egrep -i 'solv|ager|net'
dbus-org.freedesktop.network1.service  alias           -
display-manager.service                enabled         enabled
network.service                        alias           -
systemd-network-generator.service      disabled        disabled
systemd-networkd-wait-online.service   masked          disabled
systemd-networkd.service               enabled         disabled
systemd-resolved.service               disabled        disabled
systemd-networkd.socket                enabled         disabled
network-online.target                  static          -
network-pre.target                     static          -
network.target                         static          -
#

**malcolmlewis** · 22-Mar-2022, 12:59

Originally Posted by docbobo

Well, I don't believe that vagrant is using either ignition or combustion. My question is really about: how to use the supposed mechanisms to provision the instances with a static ip address instead of DHCP...

But thank you anyway!

Hi
No, but vagrant allocates the required ip address for the system and k3s to use, so Proxmox cannot do the same?

I see on one of the nodes;

Code:

worker-4:~ # cat /etc/sysconfig/network/ifcfg-eth0
BOOTPROTO='dhcp'
STARTMODE='auto'

worker-4:~ # cat /etc/sysconfig/network/ifcfg-eth1
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
BOOTPROTO='static'
IPADDR='192.168.10.183'
NETMASK='255.255.255.0'
DEVICE='eth1'
PEERDNS='no'
STARTMODE='auto'
USERCONTROL='no'
#VAGRANT-END

eth0 the vagrant management interface, eth1 for k3s.

**malcolmlewis** · 22-Mar-2022, 13:21

Hi
So I'm guessing Proxmox is more like SUSE & Rancher Harvester? So there you can use vlans in my brief run of Harvester testing/playing. I just used vlan1 and untagged so it picked up the dhcp allocation for a k3s cluster.

I suggest heading over to join the SUSE & Rancher Community as there are a number of folks using Proxmox, they may have further information? https://community.suse.com