ansible-role-systemd_networkd not support vip /32

[Corentin Joubert]

Hello,
I noticed that the ansible-role-systemd_networkd role does not support ip management in /32.

here are the variables I've used:

systemd_run_networkd: true

systemd_networks:
  - interface: "ens18"
    address: "10.0.100.11"
    netmask: "255.255.255.255"
    gateway: "10.0.100.254"
    mtu: 1500
    usedns: true

systemd_resolved:
  DNS: "10.0.0.10"
  FallbackDNS: "9.9.9.9 1.1.1.1"

this format is not valid for an ip in /32 :

[Match]
Name=ens18

[Network]
Address=10.0.100.11/32
Gateway=10.1.100.254
DNS=10.1.10.1

According to my research and testing, it should be in this format:

[Match]
Name=ens18

[Network]
Gateway=10.1.100.254

[Address]
Address=10.0.100.11
Peer=10.1.100.254/32 # Gateway

 We'll have to see about adding /32 ip management to the template.

[Dmitriy Rabotyagov (noonedeadpunk)]

Hi,

I'm not sure about the context of systemd_networkd usage, but I assume that having var like this should lead to result you've posted:

systemd_networks:
  - interface: "ens18"
    mtu: 1500
    usedns: true
    config_overrides:
      Network:
        Gateway: 10.1.100.254
      Address:
        Address: 10.0.100.11
        Peer: 10.1.100.254/32

Any contributions/proposals to optimize the flow are very welcome :)