eth0 Disconnected on Kali Linux ARM

Question

I have recently installed Kali Linux ARM on a flash drive for my Rasberry pi. Upon boot up, I ran into the device not managed problem. If you do not know what this is, it is where by default Linux does not manage Ethernet connections.

You can read the article I used as my solution here:

How to fix Wired Network interface "Device not managed" error in Debian or Kali Linux? | BlackMore Ops

I went through all the steps of the article, however when I enter service network-manager restart I do not get any prompts from the terminal as the article does. It just completes the command.

Now, my Ethernet reads disconnected when on the physical layer it is certainly connected. If you want proof that all the steps in the article are completed, my /etc/NetworkManager/NetworkManager.conf file currently is this:

[main] 
plugins=ifupdown,keyfile 

[ifupdown] 
managed=true 

I assume there are some discrepancies between normal Linux and ARM Linux causing this problem. However currently I cannot connect to the Internet with my RasPi, are there any solutions to it simply reading disconnected?

Solution

First, open the Network Manager configuration file in /etc/NetworkManager with a text editor, and set "managed=false". Then edit network configuration file /etc/network/interfaces like this:

# The loopback network interface 
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet dhcp

Then reboot your computer. Check that Ethernet cable is good and auto negotiation is enabled via command ethtool eth0.

Comments

[Anshu]

The joy of NetworkManager. I have been known to nuke it from high orbit and manually set up the interface and just use the network service. BUT, this makes moving from one network to another painful. Maybe someone who knows how to actually make NM work will chime in.

[Colin Stricker]

@Xalorous r/linuxquestions has so far suggested I just use wicd and nuke NetworkManager all together. This seems like the best option thus far. It would be nice to find a solution however.

[Anshu]

I don't know wicd, but I'm in a server environment, and our configs are static. It irritates me that so much has been shifted to NetworkManager on Servers. Servers are typically static on network config. NetworkManager, with all of its bells and whistles, seems to serve the mobile segment more. NetworkManager suits when changing from network to network as you go from home to school/work and then whatever hangout. Of course Kali is pentesting environment, so manually setting the network settings should be within the operator's skillset.

[VocalFan]

What is the output of service network-manager status?

[Colin Stricker]

@JigglyNaga network-manager: unrecognized service

[VocalFan]

Is network-manager even installed? (dpkg -l network-manager) Did you run the service network-manager ... commands as root?

[Colin Stricker]

@JigglyNaga I dunno, I've moved over to Rasbian now, and the issue persists even after configuring for DHCP. It's odd, as the physical layer is good. Since it's Rasbian, I will be making a new question for this. This no longer involves NetworkManager nor Kali Linux.