Ah... Kali Linux...
I always loved Backtrack. Back in the days, it booted in CLI with no network at all. OffSec motto: "The quiter you are, the better you are able to listen". Makes absolute sens for a pentest oriented distro isn't it?
Then cames the kikou-lols, the n00bs, the posers, the kiddies, the players, the Sunday hackers, and the beloved distro got mainstream.
Now... Kali is sexy, don't get me wrong, I still love it. But FFS: it boots by default in graphic mode and starts all the fucking NICs it founds. But that's not enough... no.... it also starts the fucking DHCP client.
How on Earth can you be quite and able to listen with such a behavior?
Now... awright, let's turn back to descent behavior and boot in the old-style backtrack way. Preventing GDM and the ridiculous Gnome3 is easy. But NetworkManager is a hard beast to kill.
Renaming links in /etc/rc*.d, sysv-rc-conf or chkconfig to disable NetworkManager didn't work. Despite the fucking service to be disabled, it still starts at boot. Interesting hey? I had to "mv NetworkManager.service NetworkManager.service.DISABLED.OSTI.TABARNAK" in /lib/systemd/system to prevent it to start.
But hey? that can't be a solution: you're not able to start the service thereafter should you want to use it.
Well, fuck that, I never liked NetworkManager in the first place. Let's use that good old wicd instead. Works like a charm... unless you want to use the CLI wicd-curses client. It's dead Jim.
I remember I fixed it once, some time ago, when playing with BlackArch. I found a diff that was fixin' the Python code, needed to do something more... should have take notes 'cause now, I'm not fucking able to find the reference again.
Sometimes I feel so tired...