Bug? After setting OMV to a fixed internal IP the machine is reachable both on the fixed and the old DHCP address!

1. offizieller Beitrag

    Hi all,


    I have installed an OMV 5 machine from scratch recently and at the beginning it had only a dynamic ip address given from my router, 192.168.22.166 - which was fine.


    Then I changed the Ip to "static": 192.168.22.3 - and now I can reach the machine via both addresses!


    That should not be because it uses up too much address space...


    What can I do?


    So far, I don't remember a IPv4 Ethernet could have two IPs of the same subnet at the same time.


    If it's a feature, I think OMV should offer a way to turn off the DHCP address.


    Andreas

  • ande

    Hat den Titel des Themas von „Bug? After setting OMV to a fixed internal IP the machioen is reachable both on the fixed and the old DHCP address!“ zu „Bug? After setting OMV to a fixed internal IP the machine is reachable both on the fixed and the old DHCP address!“ geändert.
    • Offizieller Beitrag

    Not sure how you installed or what you installed on but good chance is the dhcpcd5 package is installed. I would purge it.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    I didn't install any extra packages, just what came in the OMV 5 iso.


    My ISP has IPv6 but I was talking to my OMV via the IPv4 address only.


    However, emptying the DHCP leases on the rpouter and restarting OMV seems to have done the trick.


    Might be nice if the UI told us that we need to reboot...


    Thanks!

  • ande

    Hat das Label gelöst hinzugefügt.
    • Offizieller Beitrag
    Zitat von ande

    Might be nice if the UI told us that we need to reboot...

    I normally don't need to when switching to static IP.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Offizieller Beitrag
    Zitat von ande

    Yes but I was not aware that the old IP remained there and made services still accessible. Could turn out as a security problem one day for someone.. not that I want to be nagging..

    Security problem? OMV configures services to listen on all network adapters by default. And since this is the same network adapter, how could one IP address be secure and the other not? If you are opening firewall ports for the dhcp address, I would stop doing that. Rebooting after a major network change should just be habit even if not completely necessary.

    omv 7.7.10-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0.2 | kvm 7.1.8 | compose 7.6.10 | cterm 7.8.7 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.3.1


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!

Benutzerkonto erstellen Anmelden