wifi card on ubuntu bash on windows 10

[htanh034]

how to receive the wifi card on ubuntu bash on windows 10 >>to using wifite (kali tools)

[jackchammons]

Can you please provide more information regarding your issue? See our contributing.md for help.

[rodrymbo]

Just a note: so far Windows handles all networking for WSL. None of the usual linux networking commands work (though ping and traceroute can work if one runs bash.exe elevated). If Windows is configured to use wifi, WSL/bash.exe should use it without any trouble. The main problem people have is if DNS is misconfigured in WSL (/etc/resolv.conf), it looks like no networking is functioning.

If the use case is pentesting a wifi subnet, that would make a good argument for fixing WSL so such tools can work, especially if they are linux-only.

[fpqc]

I do wonder if one day in the distant future, MS will figure out a way to make the devices available to WSL, but using the Windows-loaded drivers rather than trying to use the Linux ones. It would probably require some kind of translation of the WinNT HAL to something that udev could read. I tried reading up a bit on how Linux provides a usermode interface to drivers, but it seems like it's split up across all the different types of devices.

[joowdx]

Hi. I have the same issue.

When running wifite it gives me these errors.

 [+] scanning for wireless devices...
 [!] no wireless interfaces were found.
 [!] you need to plug in a wifi device or install drivers.
 [+] quitting

Does bash on windows have any direct access to physical hardware like wireless card?
Running parted too has its own errors.

[aseering]

Hi @joowdx -- no, WSL does not, for the most part, have direct physical access to your hardware.

Recent Insider builds just gained direct physical access to serial ports -- I realize that's not what you're asking about here, but it's a step in that direction :-)

[sunilmut]

@joowdx - Thanks for your post and trying WSL. Thanks @aseering for pitching in. So, I got curious as to what is this tool is using that is not implemented. And, it looks like a bunch of SIOCGxxxxx IOCTL's. Here is a snippet from the strace. Would you mind opening a User Voice ticket for this? We use User voice page to help us prioritize future work, depending on the demand.

wifite.tr.1370:readlink("/usr/bin/python2.7", 0x7fffd75d0d50, 4096) = -1 EINVAL (Invalid argument)
wifite.tr.1370:readlink("/usr/bin/wifite", 0x7fffd75cee80, 4096) = -1 EINVAL (Invalid argument)
wifite.tr.1383:ioctl(3, SIOCGIWNAME, 0x7fffc3d3b760)   = -1 EINVAL (Invalid argument)
wifite.tr.1383:ioctl(3, SIOCGIWNAME, 0x7fffc3d3b760)   = -1 EINVAL (Invalid argument)
wifite.tr.1391:ioctl(3, SIOCGIWPRIV, 0x7fffe5e5d5d0)   = -1 EINVAL (Invalid argument)
wifite.tr.1391:ioctl(3, SIOCGIWPRIV, 0x7fffe5e5d5d0)   = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMETRIC, {ifr_name="eth0"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMAP, {ifr_name="eth0"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMAP, {ifr_name="eth0"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFTXQLEN, {ifr_name="eth0"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(3, SIOCGIFDSTADDR, {ifr_name="eth0"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMETRIC, {ifr_name="lo"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMAP, {ifr_name="lo"})   = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFMAP, {ifr_name="lo"})   = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(4, SIOCGIFTXQLEN, {ifr_name="lo"}) = -1 EINVAL (Invalid argument)
wifite.tr.1393:ioctl(3, SIOCGIFDSTADDR, {ifr_name="lo"}) = -1 EINVAL (Invalid argument)
wifite.tr.1397:ioctl(3, SIOCGIWNAME, 0x7ffff2442480)   = -1 EINVAL (Invalid argument)
wifite.tr.1397:ioctl(3, SIOCGIWNAME, 0x7ffff2442480)   = -1 EINVAL (Invalid argument)

[joowdx]

Thanks @aseering. Maybe i'll just have to wait for the real update :) Can't stand having a test build as my main OS.

I tried searching and find somewhat similar request here. And thank you @sunilmut

edit: I was wrong. that link only requests for /dev devices or storage devices if i'm not mistaken but as @aseering have said, if recent insider builds have now access to serial ports then maybe it's not a problem for wifite or any similar tools anymore since you can just simply use usb dongles.
I want to try it myself though.

[ahrherrera]

Hi, still in Windows 10 Fall Creators Update wifite is not recognizing wireless interfaces. Should I enable manually? In that case, how?

[andb0t]

Has there been any progress on this? Unfortunately, personally, I'm not a WSL/windows expert, so I think I cannot contribute. But I would greatly appreciate if this were fixed/implemented ;)

[jrgarga]

Hello ?

[aseering]

Hi! I don't work at Microsoft, but their suggestion above is to follow up on this via UserVoice.

[Alword]

UserVoice link Add Wireless Device Support

[therealkenc]

Be sure to post the use case over in UserVoice (sic), because it helps/matters, versus just voting or (sigh) +1ing. For example, the ask here was for wifite, which is (a) defunct and (b) probably not going to garner a MSFT/WSL priority rush due to its nature. People on UserVoice right now are basically variation #1349. If you want 802.11 capture install WireShark on Windows and away you go. But it is hard to square "I'm new to Windows/WSL" a couple of posts back with "I want to do OSI layer 2 instrumentation" in the same breath. So I think there is some disjoint here. Maybe there are some use cases (not saying there isn't) but "iwlist wifi0 ap" isn't a use case, it's a command. Start the sentence with "I am trying to... [end result you're trying to accomplish]". "Pen testing" isn't a use case either; it's a general statement that doesn't say what one is trying to accomplish. "I'm trying to get my neighbor's WiFi key" is actually a perfectly valid answer. But there's perfectly good ways to do that on Windows already, so....

[cybaware]

somthing new at this case? #wlan card for WSL/Kali

[Lucky-00]

somthing new at this case? #wlan card for WSL/Kali

Sodium hypobromite

[buddha314]

@therealkenc
All UserVoice links are 404. Where should we upvote this issue?

[benhillis]

We are using GitHub for bug reports and feature requests now.

[buddha314]

So is this the base issue I should watch? Updates will be here?

[montebhoover]

If you're still looking for use cases, I was hoping to use WSL to quickly run iwconfig and measure wifi signal strength in dBm. Came to this issue via #4313.

[SmartBoy84]

If you're still looking for use cases, I was hoping to use WSL to quickly run iwconfig and measure wifi signal strength in dBm. Came to this issue via #4313.

Somebody there has pointed to this issue... ARGHHHH

[jrgarga]

what you mean closed ? did I missed the solution here.

[SmartBoy84]

???

[IS2511]

Why is the issue closed? It's nowhere near working! 😕

[drop-shell]

wsl is useless for basically everything you would need to use it for.

[therealkenc]

This was closed since it was sent to UserVoice, which no longer exists. Academically the request ought have an open landing zone. The ask is analogy this. Which you'll note has been open since 2012. For a reason.

Here's the thing: You'll see WiFi passthrough on a QEMU/KVM Linux host with a Linux guest before you see it on a Windows host and WSL guest. As an exercise, consider what such a thing would look like. The smart play here is to subscribe #2195, which, with a dedicated WiFi USB adapter it might be hypothetically possible.

This gets locked following the first contentless +1 post. Upvote the OP. Or better, upvote #2195.

[trescorion]

Is there any way to fix this issue? As fas as read there is not but just asking :D

[mirusky]

And still no progress. Any work around...