OMV 5 new behavior

  • Hi all!


    I'm doing an early test of OMV 5.2.3-2 through an upgrade from version 4. I've been able to see a few issues along the upgrade and was able to fix them all, but something caught my attention.


    When creating my bond (I use 802.3ad LACP) I noticed that the MAC address gets auto-generated, instead of deriving it from the 1st NIC. Here's a snapshot I grabbed from iLO:


    nic-cap.PNG
    The newly generated MAC is highlighted. I don't actually see any ill side-effect with this, other than the IP changing for those that use DHCP and maybe those that prefer to use the physical MAC (like me).


    Does anyone knows if this is by design and expected?

    Absolutely no support through PMs!!
    I work for the HPE R&D division. Have tech questions about ProLiant servers? Ask me!
    Learn more about HPE's iLO included in all ProLiant servers.

    Edited once, last by Spy Alelo ().

  • Quick look at the code, looks like it should be using the mac address of the primary adapter. Not sure why it isn’t. I don’t see anywhere that would generate a mac address.

    omv 5.3.9 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • I know right? Is so bizarre, I don't even know where to start on trying to figure this out.


    As you said, I don't see where it would generate this or even why.


    I did see an impact that this would have for me, and that's when using WOL. The app I use wouldn't be able to determine if the server is up since it has use the the physical MAC to power it up. I got scripts on another server that checks those things and powers it up to RSYNC files from one to the other, this will be a challenge.

    Absolutely no support through PMs!!
    I work for the HPE R&D division. Have tech questions about ProLiant servers? Ask me!
    Learn more about HPE's iLO included in all ProLiant servers.

  • From what I can tell on my test VM, this is a behavior of systemd-networkd. A new mac address isn't stored anywhere in OMV-controlled config files.

    omv 5.3.9 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

  • This is probably the expected behavior for systemd-networkd. Since OMV 4.x didn't use systemd-networkd, I'm not sure if it is a new default.

    omv 5.3.9 usul | 64 bit | 5.3 proxmox kernel | omvextrasorg 5.2.6
    omv-extras.org plugins source code and issue tracker - github


    Please read this before posting a question.
    Please don't PM for support... Too many PMs!

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!