Kali linux wsl wifi

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wifi card on ubuntu bash on windows 10 #1077

wifi card on ubuntu bash on windows 10 #1077

Comments

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

The text was updated successfully, but these errors were encountered:

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.

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.

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.

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 🙂

@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, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFMAP, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFMAP, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFTXQLEN, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(3, SIOCGIFDSTADDR, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFMETRIC, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFMAP, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFMAP, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(4, SIOCGIFTXQLEN, ) = -1 EINVAL (Invalid argument) wifite.tr.1393:ioctl(3, SIOCGIFDSTADDR, ) = -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) 

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.

Источник

Kali Linux(WSL) not recognizing wireless adapter

I have installed Kali Linux on my Windows 10 laptop through the Microsoft store. Now when I use the command iwconfig , it says no wireless extensions next wifi0, wifi1 and wifi2. So I thought my built-in wireless adapter is not capable of monitor mode, however, I have Microsoft Network Monitor 3.4 installed in my Laptop and it successfully captures packets, so to my understanding, my built-in adapter is capable of monitor mode. My question is essentially why does it say «no wireless extensions» because I won’t be able to use airmon-ng unless this is resolved. I’m relatively new to Kali Linux so please forgive if my understanding of the situation is incorrect.

1 Answer 1

This feature is not (yet) implemented in WSL.

fpqc commented on 21 Sep 2016

The way it works right now, the Win32-side networking settings control the kernel, which then controls the LX-side networking. There are no real networking devices set up in /dev on the LX side, at the moment at least.

There are many duplicates of the same type in the WSL issue tracker on github:

You must log in to answer this question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.12.43529

Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.
This site is not affiliated with Linus Torvalds or The Open Group in any way.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Are USB Wi-Fi adapters compatible with Kali in WSL2

Will WSL automatically recognize a USB Wi-Fi adapter and will I be able to use it. If not how can I direct it to WSL? I want to use an external USB wifi adapter because you can’t use the same adapter as the host for wireless auditing in Kali using programmes like Wifite.

2 Answers 2

Yes, it is possible to use a USB Wi-Fi adapter but you will have some setup to do.

1. Open Hyper-V Manager as Administrator.
2. Go to Virtual Switch Manager.
3. Select WSL.
4. Change the connection type to External network.
5. Choose your Wi-Fi adapter.
6. If you want, untick the box that says Allow management operating system to share this network adapter.
7. Press OK to save the changes and exit Hyper-V Manager.
8. Open WSL.
9. Then run these 2 commands.

sudo ip addr flush dev eth0 sudo dhclient eth0 

1. Check if the internet connection is working by pinging google.com
2. If it doesn’t try reopening WSL.
3. If it still doesn’t work, change the nameserver in /etc/resolve.conf to a different DNS like Google (8.8.8.8) or Cloudflare (1.1.1.1)

Okay so, I edited the kernel itself to allow you to actually be able to use WiFi adapters as well as loadable modules, etc in WSL2

While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes. — From Review

You must log in to answer this question.

Related

Hot Network Questions

Subscribe to RSS

To subscribe to this RSS feed, copy and paste this URL into your RSS reader.

Site design / logo © 2023 Stack Exchange Inc; user contributions licensed under CC BY-SA . rev 2023.7.12.43529

Linux is a registered trademark of Linus Torvalds. UNIX is a registered trademark of The Open Group.
This site is not affiliated with Linus Torvalds or The Open Group in any way.

By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.

Источник

Saved searches

Use saved searches to filter your results more quickly

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kali Linux on windows 10 WSL is not detecting WI-FI. cant able practice wifi hacking. #7400

Kali Linux on windows 10 WSL is not detecting WI-FI. cant able practice wifi hacking. #7400

Comments

Windows Build Number

Microsoft Windows [Version 10.0.19043.1165]

WSL Version

Kernel Version

Distro Version

Other Software

Repro Steps

bond0 no wireless extensions.

lo no wireless extensions.

eth0 no wireless extensions.

dummy0 no wireless extensions.

1. when I run
   └─# wifite
   . .
   .´ · . . · . wifite2 2.5.8 : : : (¯) : : : a wireless auditor by derv82 . · /¯\ ´ · .´ maintained by kimocoder /¯¯¯\ ´ https://github.com/kimocoder/wifite2

[!] Warning: Recommended app pyrit was not found. install @ https://github.com/JPaulMora/Pyrit/wiki
[!] Warning: Recommended app hcxdumptool was not found. install @ apt install hcxdumptool
[!] Warning: Recommended app hcxpcapngtool was not found. install @ apt install hcxtools

[+] Checking airmon-ng.
[!] airmon-ng did not find any wireless interfaces
[!] Make sure your wireless device is connected
[!] See http://www.aircrack-ng.org/doku.php?id=airmon-ng for more info

[!] Error: airmon-ng did not find any wireless interfaces

[!] Traceback (most recent call last):
[!] File «/usr/lib/python3/dist-packages/wifite/main.py», line 97, in entry_point
[!] wifite.start()
[!] File «/usr/lib/python3/dist-packages/wifite/main.py», line 51, in start
[!] Configuration.get_monitor_mode_interface()
[!] File «/usr/lib/python3/dist-packages/wifite/config.py», line 167, in get_monitor_mode_interface
[!] cls.interface = Airmon.ask()
[!] File «/usr/lib/python3/dist-packages/wifite/tools/airmon.py», line 313, in ask
[!] raise Exception(‘airmon-ng did not find any wireless interfaces’)
[!] Exception: airmon-ng did not find any wireless interfaces

so I cant able to use wifi of my windows in my wsl so that I can practice wifi hacking.

Expected Behavior

evert wsl must and should have a feature of running the wifi of windows.
so that security researcher can perform wifi hacking with authorization

Actual Behavior

cant able to use wifi of windows 10

Diagnostic Logs

The text was updated successfully, but these errors were encountered:

Источник