Unable to add alias IP in OMV5

svetsch · 5. April 2020

Hi,

I'm currently unable to add an IP alias to my OMV5 blank install.

When I try to add a VLAN adress through the GUI everything seems fine until save:

Before apply, I have:

then:

Then I loose the network completely.

Before changes, I have:

Code

ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 10:c3:7b:92:6a:ac brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.12/24 brd 192.168.1.255 scope global enp3s0
           valid_lft forever preferred_lft forever
    3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
        link/ether 02:42:32:ff:71:a9 brd ff:ff:ff:ff:ff:ff
        inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
           valid_lft forever preferred_lft forever
    5: vetha0ebe1d@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
        link/ether 82:c9:c1:b9:73:a4 brd ff:ff:ff:ff:ff:ff link-netnsid 0

Alles anzeigen

Content of /etc/systemd/network

Code

/etc/systemd/network/10-openmediavault-enp3s0.link
    [Match]
    MACAddress=10:c3:7b:92:6a:ac

    [Link]
    NamePolicy=keep kernel database onboard slot path
    MACAddressPolicy=persistent
    
/etc/systemd/network/10-openmediavault-enp3s0.network
    [Match]
    Name=enp3s0

    [Network]
    Address=192.168.1.12/24
    Gateway=192.168.1.1
    IPv6AcceptRA=no
    LinkLocalAddressing=no
    DNS=8.8.8.8
    Domains=home

    [Link]

    [IPv6Prefix]

Alles anzeigen

After changes, and lost network, I have:

Code

ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 10:c3:7b:92:6a:ac brd ff:ff:ff:ff:ff:ff
    3: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
        link/ether 02:42:32:ff:71:a9 brd ff:ff:ff:ff:ff:ff
    5: vetha0ebe1d@if4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
        link/ether 82:c9:c1:b9:73:a4 brd ff:ff:ff:ff:ff:ff link-netnsid 0
    6: enp3s0.1@vetha0ebe1d: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ether 82:c9:c1:b9:73:a4 brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.13/24 brd 192.168.1.255 scope global enp3s0.1
           valid_lft forever preferred_lft forever

Alles anzeigen

Content of /etc/systemd/network

Code

/etc/systemd/network/10-openmediavault-enp3s0.link
    [Match]
    MACAddress=10:c3:7b:92:6a:ac

    [Link]
    NamePolicy=keep kernel database onboard slot path
    MACAddressPolicy=persistent

    
/etc/systemd/network/10-openmediavault-enp3s0.network
    [Network]
    VLAN=enp3s0.1

/etc/systemd/network/10-openmediavault-enp3s0.1.netdev
    [NetDev]
    Name=enp3s0.1
    Kind=vlan

    [VLAN]
    Id=1
    
/etc/systemd/network/10-openmediavault-enp3s0.1.network
    [Match]
    Name=enp3s0.1

    [Network]
    Address=192.168.1.13/24
    Gateway=192.168.1.1
    IPv6AcceptRA=no
    LinkLocalAddressing=no
    DNS=8.8.8.8
    Domains=home

    [Link]

    [IPv6Prefix]

Alles anzeigen

Ater reboot, I have:

Code

ip a
    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
        link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
        inet 127.0.0.1/8 scope host lo
           valid_lft forever preferred_lft forever
        inet6 ::1/128 scope host 
           valid_lft forever preferred_lft forever
    2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
        link/ether 10:c3:7b:92:6a:ac brd ff:ff:ff:ff:ff:ff
    3: enp3s0.1@enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
        link/ether 10:c3:7b:92:6a:ac brd ff:ff:ff:ff:ff:ff
        inet 192.168.1.13/24 brd 192.168.1.255 scope global enp3s0.1
           valid_lft forever preferred_lft forever
    4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default 
        link/ether 02:42:55:86:22:59 brd ff:ff:ff:ff:ff:ff
        inet 172.17.0.1/16 brd 172.17.255.255 scope global docker0
           valid_lft forever preferred_lft forever
    6: vethf5d5370@if5: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master docker0 state UP group default 
        link/ether 82:46:43:16:08:1d brd ff:ff:ff:ff:ff:ff link-netnsid 0

Alles anzeigen

In order to get network back, I had to remove content of /etc/systemd/network/*, reboot and use omv-firstaid to create the default network interface again.

I'm using:

OMV 5.3.9-1

Kernel 5.4.0-0.bpo.4-amd64

on intel i7 with 16GB of ram

system report attached.

Docker and portainer are installed and working fine

Any help/hints are welcome !

Thanks

svetsch · 7. April 2020

Hi,

I'm wondering if I misuse the VLAN feature.

My goal is simply to add a second IP to my network interface. An alias IP.

I finally managed to make it work by adding an address line in the file:

Code

/etc/systemd/network/10-openmediavault-enp3s0.network
    [Match]
    Name=enp3s0

    [Network]
    Address=192.168.1.12/24
    Address=192.168.1.13/24
    Gateway=192.168.1.1
    IPv6AcceptRA=no
    LinkLocalAddressing=no
    DNS=8.8.8.8
    Domains=home

    [Link]

    [IPv6Prefix]

Alles anzeigen

But how can I prevent OMV to overwrite it?

votdev · 7. April 2020

That's not possible.

As a workaround you can force SaltStack to use another SLS file (https://github.com/openmediava…emd-networkd/init.sls#L24). Check the SaltStack documentation how to do that. But in that case the whole network deployment is switched off. That's why i won't post the exact workflow here.

svetsch · 7. April 2020

Thanks for answer.

I finally added a copy of the network file renamed to 05-custom-enp3s0.network.

My file is taken first and the omv one seems ignored at runtime, that's ok for me now. As the config cleaning only targets '^\d+-openmediavault-(.+)\.network$' pattern, my custom file is not removed.

Is it a feature (alias ip) that is planned sooner or later in OMV ?

I would suggest to support for example a comma-separated set of IPs in the address field of the interface.

Unable to add alias IP in OMV5

Jetzt mitmachen!

Tags