Shell Bash on Windows 10

[ngomaichi]

Yesterday, August 4, Microsoft made available its new Windows 10 update, “Anniversary”, in which they include the bash console in beta, which has already been more than 6 months. As I mentioned in another of my articles, I had little hope in this Shell, and my fears have been fully confirmed, everything related to network interfaces does not work. After verifying that the net-tools were installed, and installing the wireless-tools, and the iw, wpasupplicant, hostapd, dhcpcd, dnsmasq, arp-scan, lighttpd packages and the aircrack suite, the conclusion is that everything related to network interfaces does not work. If we type a simple ifconfig, it gives us the first one in the forehead. “Attention: cannot open /proc/net/dev (No such file or directory). Limited output.” If we try with airmon-ng from the aircrack suite, it does not detect any interface. If we do an iwconfig, it seems that it detects something, although it is not real, nothing to scratch. I have even tried to set up a web server with lighttpd to see if by chance it loaded the web on localhost, since in Windows I have the interfaces active, but nothing at all. And already of hostapd, arp-scan, etc, we forget, any Linux package in which an interface has to do with it, will not work for you. As I said before, I did not have great hopes in this Shell, since they had announced that it was not going to be a virtualized Shell but that it would be independent of Windows, but then we enter the conflicts of kernels, because the Linux kernel does not exist, and Linux packages cannot handle the Windows kernel because obviously they are made for Linux. The question that arises in me is ¿For what is then this bash Shell in Windows good for? It is in beta mode, but I do not think this will improve. ¡Good fun!

[Mystique]

I have a question, why do you want Windows 10 to do everything you mentioned?