Can't access internet in kali virtualbox

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.

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.

1

The solution was this

vi /etc/NetworkManager/NetworkManager.conf

Change false to true

And then

service network-manager restart 

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.

0

In the VirtualBox network settings, I had to check "Cable Connected" (like suggested by another answer: ).

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)

0

set to Bridged Adapter in network, for the vm and open terminal and the terminal to type --> service network-manager restart

1

1. You can try the following commands: service network-manager restart
2. If it is Kali Linux (Debian), you need to use the following command: service networking restart
3. 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.

2

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password Submit

Post as a guest

Post Your Answer Discard

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy