Interface trouble, eth1 doesn't exist

Question

I add in virtualbox 2 interfaces like bridge, Internal network 192.168.. and external 195...*

Internal config:

auto eth0
iface eth0 inet static
address 192.168.*.250
netmask 255.255.255.0
network 192.168.*.0
broadcast 192.168.*.255
gateway 192.168.*.254

External config:

auto eth1
iface eth1 inet static
address 195.*.*.182
netmask 195.*.255.248
network 195.*.*.176
broadcast 195.*.*.183
gateway 195.*.*.177

Now if i restart the networking eth0 successfull is up, but eth1 make the error:

root@Tudor-LX:/home/theo# /etc/init.d/networking restart
 * Running /etc/init.d/networking restart is deprecated because it may not enable again some interfaces
 * Reconfiguring network interfaces... 
SIOCSIIFADDR: No such device
eth1: ERROR while getting interface flags: No such device 
SOICSIFNETMASK: No such device 
SIOCSIFBRDADDR: No such device 
eth1: Error while getting interface flags: No such device 
eth1: Error while getting interface flags: No such device 
Failed to bring up eth1. 
ssh stop/waiting 
ssh start/running, process 1260

Does eth1 exist on your host machine? (assuming that external is your host) — Lekensteyn, Jul 25 '11 at 09:17

score 1 · Answer 1 · edited Apr 13 '17 at 12:23

1

Run this...

How to restart the networking service?

Do not run this in a root shell, just run it using sudo. I've seen the SIO errors the first time you run the command, but not the second time. You may have to run it twice in a row.

I would also comment out the auto eth statements.

edited Apr 13 '17 at 12:23

Community

1

answered Jul 24 '11 at 15:44

Aric

139

1

auto eth* makes ifup -a bring up these interfaces. Why should it be disabled? – Lekensteyn Jul 24 '11 at 21:05
auto eth is for DHCP. You've configured these for static and DHCP at the same time. That's probably the source of the problem. – Aric Jul 25 '11 at 00:31
2

no, auto eth0 does not enable DHCP, for that you need to put in iface eth0 inet dhcp which is not desired here. Please read to the manual page interfaces(5). – Lekensteyn Jul 25 '11 at 09:13
I stand corrected; you are right. Okay, so if you do an ifconfig, what is the output? Is eth1 listed? Is the link up? – Aric Jul 26 '11 at 02:54

score -1 · Answer 2 · answered Apr 06 '13 at 03:48

I believe saying that auto eth is for DHCP only is WRONG!

The auto = just means to: Automatically Launch The Ethernet Device Listed!

I Setup Mines Similar! Maybe this can help!

Using AUTO & STATIC IP!:

auto eth0
iface eth0 inet static
        address 192.168.x.x
        netmask 255.255.255.0

#########

    auto eth0:1
    iface eth0:1 inet static
    address 192.168.x.x
    netmask 255.255.255.0
    gateway 192.168.0.1
    dns-nameservers 8.8.8.8 8.8.4.4

Both Host & eth0:1 - Have There Own Static IP!

With eth1. I will receive the same error!

score -1 · Answer 3 · edited Apr 13 '15 at 15:09

@Toader hey, have you checked lsmod result? it will list out all the modules which are currently loaded in kernel. If it's not then try to load it manually by this command as follow:

insmod /path/to/module

Path is like:

/lib/modules/kernel-version-directory/kernel/drivers/net/ethernet/intel/module-name/module-name.ko

Module Name: You can check your module name with lshw -C network command to corresponding interface. In my case it is Intel. You can also try same with

modprobe module-name

Then after restarting the the networking interface you can check it with ifconfig.

Interface trouble, eth1 doesn't exist

3 Answers3