1

So i am currently facing a problem booting my 2016.2 Kali linux: 

[FAILED] Failed to start Raise network interfaces.

I have set a static ip addressing in /etc/network/interfaces file by writing:

auto eth0
iface eth0 inter static 
address x.x.x.x
netmask x.x.x.x
gateway x.x.x.x

according to this source:source there is some problem with predictable network interface names, I couldn't really understand what really is the problem, but I wanted to use my eth0 interface name so adding /etc/udev/rules.d/10-network.rules file with the following: SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="ff:ff:ff:ff:ff:ff", NAME="eth0" as suggested here by JonnyTischbein but with no success.

Could you please provide me with a good explanation about the predictable interfaces name problem, and what is the solution I should do in my cause?

are the lines in the /etc/network/interfaces files causing this problem?

Improve this question
3
  • 1
    Did you correct the MAC address (ff:ff:ff:ff:ff:ff) and interface name (eth0) as mentioned on that page? Commented Jan 21, 2017 at 0:14
  • @JuliePelletier Yes, of course I did :) Commented Jan 21, 2017 at 1:18
  • Note there may be a typo in your file: inter should be inet I think? Commented Jan 21, 2017 at 4:26

1 Answer 1

Reset to default
1

Could you please provide me with a good explanation about the predictable interfaces name problem, and what is the solution I should do in my cause?

Predictable interface names isn't a problem, it's a solution to a problem. If you have multiple Ethernet interfaces, in some cases, it won't be guaranteed that eth0, eth1, eth2, etc, will be the same interfaces after a reboot. At the next boot, the kernel might detect your USB ethernet adapters in a different order reversing eth1 and eth2.

So the new naming encodes the path to the interface in hardware (such as the PCI slot number). And when detection order is not reasonably fixed, such as in the case of USB adapters, the MAC address is included in the interface name for complete disambiguation.

So, just leave out your custom udev rule and deal with a predictable interface name like ens1 rather than eth0. Enjoy your tux!

Improve this answer
1
  • Thanks for the informative answer, now it's clear to me, but could you please provide with a further explanation on how would i use ens1 instead of eth0 (what changes should I make?), plus I don't really understand how to choose a predictable name (or is it automated?) Commented Jan 21, 2017 at 12:57

You must log in to answer this question.