However, you've mentioned making some other changes, and it's also visible in the screenshot that you ran:Įcho "deb kali-rolling main non-free contrib" > /etc/apt/sources.list I.e., your local metadata for a file in the repository says that the size is "5," but by the time the file is downloaded, a mirror sync is in progress on the other end and the size is now "7". That could be what's happening (or what happened). Now from the VM you should be able to ping the host: ping 192.168.0.2Īnd from the host you should be able to ping the VM: ping 192.168.0.The screenshot shows that files obtained from the repository don't match the expected size, and indicates a potential explanation: Mirror sync in progress?. In the VM: sudo ifconfig eth0 192.168.0.3/24Ĭonfirm that you can see your new address with: sudo ifconfig eth0 Manually put the VM on the same network and see if you can ping both ways. Now you should have an address and subnet lets say windows reported your IP as 192.168.0.2 with a mask of 255.255.255.0. In windows you can do this from cmd with: ipconfig/all Also check the subnet mask (probably listed as /24 or 255.255.255.0 but it could be something else). I'm pretty surprised that you don't get an address after rebooting the VM when virtualbox is set in NAT mode.You can try to get any networking: In virtualbox set the networking to NAT and "reboot" the VM. We can come back and try to trouble shoot the bridged network but lets try to get the VM working first (since bridged mode adds some other options for why it's not working). Post the results of: sudo cat /etc/network/interfaces What are the network settings on VirtualBox?Īnd what is the output of sudo ifconfig -a? Since dhclient didn't solve the problem, you should make sure your VM is configured correctly. If this is the case you may be able to fix your problems with a single command: sudo dhclient eth0 You will most likely see an eth0 with no inet addr. First check if you have an IP address at all: sudo ifconfig -a You need to elevate your user to root in order to manage some files (like interfaces). You most likely don't have a default gateway set so your system doesn't know how to route the traffic. Your DNS servers aren't reachable (or likely aren't set at all). Keep updating and here is the result of " cat /etc/network/interfaces " and " route -n"Īfter changing the vbox settings from bridged to nat nothing changed - still don't have an ip adress. Here is an image of the output of ifconfig -a I use a bridged mode on wifi intel(R) 5100agn in advanced tab I have all allowed and I use a usb ralink wifi adapter linked to the virtual machine. I think my virtualbox settings are ok because I already surfed the internet before this problem came on but here are the settings. I tried the following: $ ping ping: unkown host Ĭat: /etc/network/interfaces: Permission denied My problem is that while I already connected Kali to the Internet and used Iceweasel many times, now, after some manipulations I did on the terminal, I can't reach the Internet anymore, even if I connect to my wifi network. I know it's based on Debian but I come from Windows so I'm new to Linux and networking in general. I'm running Kali Linux on VirtualBox and trying to learn some of its basics.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |