Le 16/08/2016 à 09:03, Rick Thomas a écrit :
Aug 14 17:02:41 sheeva systemd[1]: Starting Raise network interfaces...
Aug 14 17:02:46 sheeva ifup[893]: /sbin/ifup: waiting for lock on
/run/network/ifstate.eth0
Aug 14 17:02:49 sheeva ifup[893]: RTNETLINK answers: File exists
"RTNETLINK answers: File exists" typically happens when you try to add
an address or a route which is already exists with "ip", which is the
tool used internally by ifup.
However the interface *is* up:
Yes but the configuration may not be complete.
--------- /etc/network/interfaces ------------
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo eth0
iface lo inet loopback
# The primary network interface
allow-hotplug eth0
iface eth0 inet static
address 192.168.3.111
netmask 255.255.240.000
network 192.168.0.0
broadcast 192.168.15.255
gateway 192.168.1.1
Note that the network and broadcast options are not required. If
missing, they will be calculated from the address and netmask values.
iface eth0 inet6 static
address 2001:1234:2d2:1:f2ad:4eff:fe00:3077
netmask 64
This IPv6 address looks like an autoconfigured address calculated from
the MAC address. You should not statically assign this kind of address.
If a router in your network sends IPv6 Router Advertisements (RA) with
the prefix 2001:1234:2d2:1::/64, then the kernel may autoconfigure the
same address, so this could be the duplicate.
"ip -6 addr" shows whether an IPv6 address was statically or dynamically
assigned.
Note for Hans : the network and broadcast addresses are consistent with
the netmask.
