Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
networking.service fails to start (times out after 5 minutes) when both IPv4 and IPv6 are enabled for an interface #116
When I enable both IPv4 and IPv6 for some interface (DHCP in both cases), omv boots very slowly. The problem is networking.service. It freezes and times out after 5 minutes:
But the interface gets an IPv6 address:
Reproducible on real hardware and in VirtualBox. Installed OMV 4 on top of a minimal installation of Debian 9 using this guide: http://openmediavault.readthedocs.io/en/latest/installation/on_debian.html
I have the same issue after I changed my motherboard and had to reconfigure (enp4s0 changed to enp2s0).
But removing auto (as in refferenced) will propably dissable autostart of the network interface and make the machine after restart not available over network (if I understand correctly what auto does, it autostarts the interface on bootup?).
Before the system also needed some time to boot up but maybe I have never typed:
If I disable ipv6 with omv-firstaid all works properly.
I chose both auto (dhcpv6 and slaac?) ways for IPv6 both didn´t work.
The system gets ipv6 (fd55..., fe80..., 2003...) and can ping6 ipv6.google.com and also an ipv6 (2003) of another device in my network.
So all seems to work. But still the networking.service failed. I don´t believe this is good.
Does this apply to the same machines your using to test OMV? If yes, does the /etc/network/interfaces file looks exact the same? I'm wondering because OMV does not do any special things to the userland network stack.
The only thing that comes into mind is the systemd unit openmediavault-issue. Can you give it a try and disable this unit. Maybe this will fix the boot issue.