Newbe Dev Stack

Answer : "Drag and Drop" was introduced with the guest additions in Virtual Box 5.0. with some limitations: At the moment drag and drop is implemented for Windows- and X-Windows-based systems, both, on host and guest side. As X-Windows sports different drag and drop protocols only the most used one, XDND, is supported for now. VirtualBox Manual In addition to that only drag & drop of simple text, or files and directories of the file manager not running with administrative permissions is supported. Preliminary experimental versions of Virtual Box "Drag'N'Drop" to a Linux guest only were introduced in version 4.2 . According to the Release notes: https://www.virtualbox.org/wiki/Changelog-4.2 "Added experimental support for Drag'n'drop from the host to Linux guests. Support for more guests and for guest-to-host is planned." I did not see any newer release notes indicating that status had changed. So, Drag 'n' ...

Answer : This all looks normal to me. Anything under 10.0.0.0/8 (and also 172.16.0.0/12) are perfectly normal NAT addresses. When you put your VMs in NAT mode, the software is essentially acting as it's own dhcp server for the guest machines and will do translations to the host network, so that all the guests on a particular host share an IP with the host. Anything in any of those ranges are fair game for NAT. It appears that VMWare uses a 192.168.0.0/24 range by default, and VirtualBox uses a 10.0.0.0 range. Both are just fine, and neither is better than the other (though I personally prefer 10.0.0.0 ranges because there are 255 times more addresses available). It sounds like maybe you expected NAT mode to use the NAT between your host network and the internet, but that just doesn't happen. In fact, that is what bridge mode does. Switching to bridged mode means your VM guests are now connected directly to your home router's dhcp server for addresses. VirtualB...

Answer : The solution is to change mirror in sources.list file. For some reason the default mirror is not working. There are several mirrors of the Kali Linux repository server, all of which are spread over the world. Each time you interact with the repository, by default it will automatically use the mirror that is closest to you based on your geoip location (idea being, this will give you the best speed due to less latency). However, you can manually force kali to use a certain/different mirror rather than the one that is nearest you. Go to http://http.kali.org/README.mirrorlist where you will have a list of mirrors to chose from. First backup your current source file mv /etc/apt/sources.list /etc/apt/sources.list.backup Then create a new sources.list file vim /etc/apt/sources.list and enter new mirror. For example, old sources.list file was deb http://http.kali.org/kali kali-rolling main contrib non-free The new sources.list file can be deb http://archiv...