Hi.
Does anybody know why I get a "failed to bring up lo" during boot (the line is within the boot file) when I stange my network settings from DHCP to STATIC?
Thanks a lot.
Regards lulu
Hi.
Does anybody know why I get a "failed to bring up lo" during boot (the line is within the boot file) when I stange my network settings from DHCP to STATIC?
Thanks a lot.
Regards lulu
hi,
You can use your router to give your server a static ip address.
If you do that within OMV you will need to setup your router to accept that address so that it can really it to the rest of the network.
(within the same IP range of course)
Sorry but that wasn't the question!
Does your NIC work after the complete boot process? Can you reach the WebIF?
Is this a vm and what are you using for your virtual nic? Does the nic name (e.g. eth?) of the vm match the name of the bare metal machine???
Are you using Bridged Adapter setting?
Hi.
Yes after boot network is working and I can reach the GUI.
Yes, it is within a VM, for testing I use VMWARE, and normaly Hyper-V.
The nic name of OMV is eth0. And I use the bridged mode in VMWARE with adapter 0. Could this be the problem?
hi,
can you try a different adapter,type in your vm ?
Hmm.. I can't remember in ESXi how it worked but in Virtualbox the names for the bare metal machine and the vm have to match.
Ah ok. That is a hint. I will see.
But do you have an idea why this happens in that moment when you change from the DHCP setting to the STATIC ip in OMV?
It seems that it has something to do with the lines in the interface file:
iface lo inet6 loopback
and
allow-hotplug eth0
When I remove the lo inet6 line I don't get the failed to bring up lo error.
eth0 already configured error is gone when removing the allo-hotplug eth0.
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!