I have Kali linux installed on Virtualbox 4.3 and my host OS is fedora 19 i have bridged the VM with fedora but in kali it said that device not managed. is there anyway to fix it? thanks.
asked Nov 21, 2013 at 16:14
Add a comment
|
9 Answers
It is not broken, it is a feature. Kali comes with networking disabled by default to prevent denouncing your own presence through an unconscionable DHCP request.
You will have to start your connection with the traditional Linux means, something like
sudo ifconfig eth0 up
sudo dhclient eth0
or some such thing, depending on how you see fit.
answered Nov 21, 2013 at 17:02
-
Omg thank you so much. my eth0 would not connect to the bloody host internet wifi, I uninstalled and reinstalled VMplayer and kali like 4 times and it still wouldnt do it. thank you!– KickAssCommented May 25, 2014 at 14:43
The solution was this
vi /etc/NetworkManager/NetworkManager.conf
Change false to true
And then
service network-manager restart
answered Nov 25, 2013 at 8:26
-
6Downvoted. Connecting via an automatic service like Network manager defeats the whole purpose of using Kali, by announcing your presence to the whole world. The commands I posted establish a connection whenever you wish to, but they require a deliberate action on your part. This means you will not inadvertently announce your presence when you need to use Kali's resources. Commented Aug 24, 2018 at 6:52
-
1this command is useful for any other distros, but I echo @MariusMatutiae in preferring the manual step for the specific case of Kali Commented Dec 13, 2023 at 22:33
In the VirtualBox network settings, I had to check "Cable Connected" (like suggested by another answer: https://unix.stackexchange.com/questions/178399/no-longer-able-to-reach-the-internet-on-kali-linux/229266#229266).
-
1
connect your wireless to your pc, add the usb at usb filters in virtualbox,
it will be installed automatically start up your kali and you should see some wireless in your area.
I clicked on the task bar->Wired-Connected->Connect to accomplish this through the GUI.
I must write this here! My problem was F-Secure in host os. When I disabled it, everything started working. (Note: Before I figured this out, I did make a ton of changes in network-manager and in vb-quest-additions, based on forums suggestions)
set to Bridged Adapter in network, for the vm and open terminal and the terminal to type --> service network-manager restart
-
Welcome to SuperUser Stack Exchange. Thanks for your contribution! Before posting an answer, please make sure your suggestion was not already posted by someone else, or that the scenario is not already covered in the question. In this case, OP said "
i have bridged the VM" which indicates that they are already using the "bridge" option. Also, reading the top answer as well as the accepted answer, it makes it clear that the problem was somewhere else. I believe with these small guidelines, your future contributions to this community will be very appreciated. :) Cheers!– msbCommented Jul 8, 2019 at 18:39
- You can try the following commands:
service network-manager restart - If it is Kali Linux (Debian), you need to use the following command:
service networking restart - If it is Centos 8, you need to use the following command:
nmcli c reload
A combination of the first two pieces of advice is what worked for me.
I was originally set to a bridged connection. I wasn't able to access the internet. I followed the first person's advice and typed
sudo ifconfig eth0 up
sudo dhclient eth0
and it didn't work. Then I switched from bridged to NAT, still a no go.
Finally I vi /etc/NetworkManager/NetworkManager.conf and changed false to true and restarted the service.
Voila, the service started.
-
1Flagging a post as abusive also downvotes the post. Your recent edit doesn't help in this case...– reneCommented May 25, 2015 at 9:28
-
1Just cool down a little bit and before you step away from the keyboard please accept the pending edit on your post so we can get your post into shape– reneCommented May 25, 2015 at 9:37