Failed to start Raise network interfaces [closed]
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 4 years ago .
I am setting a Ubuntu’s VM (16.04.1 LTS) and I get an error when I try to connect from WinSCP in my windows to the VMs. The error is: developmentHost does not exist.
The network/interfaces file is this one:
If I execute a ifconfig command I get this info:
On the other side, the Virtualbox configuration for both network adapters are:
In the above picture I included the port redirection, because I want to connect with the VM withou editing the windows hosts file.
Furthermore I get this error about interfaces when I reboot.
5 Answers 5
I don’t know how to fix the failure but i can show you a shortcut to deal with this problem temporarily.
1-use this command to find out which interfaces are available in your system.
# ip link
example: lo , enp0s8
2-add following lines in /etc/network/interfaces
auto enp0s8
iface enp0s8 inet dhcp
3-restart your VM.
and it’s done.
In Ubuntu 16.04 there perhaps is no ethX interface anymore. This version now comes with the so called Predictable Network Interface Names , where the name of the interfaces can be determined by: which tries to find fixed slot topology information in certain firmware interfaces and uses them to assign fixed names to interfaces which incorporate their physical location on the mainboard. (refer to: freedesktop.org). Hence you have to find out the correct interface names by using the command ip a which prints something like:
1: lo: . 2: ensXX: . n: .
before you can configure your /etc/network/interfaces
You mentioned something about a VM, if the hardware address changes then you might have the same issue as if you changed physical hardware.
debian: Network interfaces RAISE issue on dual ethernet card 82576-CE-2T-X1
I run into a problem when setting up my dual ethernet card 82576-GE-2T-X1. I successfully make the latest driver igb and installed the module after removing the previous igb module. So, everything is fine until network raise of my /etc/network/interfaces — the raise failed.
Here is my interfaces file:
Here is the "systemctl status networking.service" message:
here is the "journalctl -xe" message:
$ sudo ifup enp1s0f1
RTNETLINK answers: File exists
ifup: failed to bring up enp1s0f1
So, the two new interfaces can’t raise (out of a total of 3, including the motherboard nic), can’t ping of course.
Does anyone has some clues? (I try to contact also the card vendor ipolex)
Thank you for your insights 🙂
1 Answer 1
ok, I figured it out:
I replaced /etc/network/interfaces from initial post with:
‘# This file describes the network interfaces available on your system
‘# and how to activate them. For more information, see interfaces(5).
source /etc/network/interfaces.d/*
‘# The loopback network interface
auto lo
iface lo inet loopback
auto enp3s0
allow-hotplug enp3s0
iface enp3s0 inet dhcp
allow-hotplug enp1s0f0
iface enp1s0f0 inet static
address 10.0.0.12
netmask 255.255.255.0
gateway 10.0.0.12
allow-hotplug enp1s0f1
iface enp1s0f1 inet static
address 192.168.0.12
netmask 255.255.255.0
gateway 192.168.0.10
and now it works like a charm. Cant’ wait to test the through output of this new card 🙂
While booting Fail to load networking module | [Failed] failed to start Raise network interfaces.
Edit: I found the solution, but I don't know why it worked if anyone can explain why this solution worked, I would be grateful. I'm interested in learning. I'm going to be reading this forum post to figure out why it worked.
This is the solution
Just putting a #
in front of source /etc/network/interfaces.d/* in the /etc/network/interfaces file, so it doesn't reference the /interfaces.d/setup file solved it for me. Everything working fine. The solution is kinda logical.
—these commands are from my computer—
This is the output of cat /etc/network/interfaces.d/setup
This is the output of cat /etc/network/interfaces
edit 3: here's another solution I foundhttps://unix.stackexchange.com/a/597415, basically the problem is the reference to eth0 in /etc/network/interfaces.d/setup. my device name is along the lines of enp#s#
I get this error while booting
When I run the above command (systemctl status networking.services) I get
This is a fresh install of debian stable on a desktop pc. My guess is the networking module is failing to load.My internet works with the Ethernet cable, If anyone knows how to fix this error, and could help me, it would be greatly appreciated, Thank you.
I don't know if this is helpful, but I did find someone with a similar error https://unix.stackexchange.com/question . interfaces
edit1: looks like that forum user has a different error code than mine though.
That /etc/network/interfaces.d/setup file definitely looks dodgy.
First, it adds a configuration for lo , the loopback interface, when that is already configured in the main /etc/network/interfaces file.
Secondly, adding configuration for etho0 / eth0 (two different spellings?!) when your interface has a different naming convention, that just doesn't sound like the kind of thing that the Debian installer would do. And I don't recall having seen that file on any Debian installation I've done.
I just checked a VM install and the virtual "enp#s#" interface it has is configured directly in the /etc/network/interfaces file, and the interfaces.d directory is empty.
Can you run dpkg -S /etc/network/interfaces.d/setup to see if it's a known part of another package you've installed? (Don't worry if it isn't. The main interfaces file doesn't show up with this command as it's not part of a package, but generated during the install process.)
Or. are you sure this is a fresh Debian install? Is there any other software, not from the Debian repository, that you've added?