-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
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
Could not put device in monitor mode #9
Comments
We try to set the card in active monitor mode. The code will fail if that is not supported. Line 224 in aab2d1f
You can check support by looking at the complete output:
|
Oh, now I see why my card is not working. That would be great if you put this information in the read me. Thanks for your work! |
@schmittner Please excuse me bumping this issue, I have the same wireless controller (Intel Wireless 8265) and have had some issues running opendrop. Does the missing active monitor mode generally imply that owl/opendrop will not at all work with my card? (I got it running, but wasn't able to discover any AirDrop peers) |
In principle, it COULD work (even though with a very very very ... bad performance). The problem is that without the active part of monitor mode, frames transmitted to your station (by other AWDL peers) will not be ACK'd and therefore transmitted up to 7 times before the other station finally gives up. While you should be able to see other AWDL peers on the link layer (as shown in the log output of |
Alright, thank you very much for that elaborate answer! That sounds plausible to me. Do you possibly know of any straightforward way of patching that active monitoring functionality for these Intel chips, similar to nexmon? |
A (hacky) idea that I have not tested: You could add a second virtual interface via |
I have the same problem. Could you recommend a USB wifi adapter (or better, a valid chipset) that supports active monitor mode? |
According to #10, the TP-Link Archer T1U seems to work. |
@ratheile the Atheros AR9280 chip (IEEE 802.11n) is recommended in the readme: https://github.com/seemoo-lab/owl/blob/master/README.md#requirements |
@schmittner, My driver only mentions "monitor" in two places, but it doesn't say anything about the ACK line that failed the other one.
|
@VelocityDesign: please read my previous comment above #9 (comment). Will pin this issue. |
I have the same network card as OP. How would I go about doing this on Ubuntu 21.04? |
I'm using Linux rather than macOS. # which iw
iw not found How can I determine if my wireless card supports monitor mode? |
|
My output looks rather different. I understand that both these devices should work, right? Instead of saying
|
I don't get the part of the other interface in regulär mode |
Hey ! I searched for the active monitor mode a lot, and I tried to find an adapter that support it. I found a GitHub that is very well maintained and I discussed the issue with the owner. Here is a link for the discussion that can help you find an adapter that will work for you. thanks to him, we now have a very modern device list that will work with OWL. |
Hello, thanks for the tip. Could you give us more information? Did your test work and was it successful with the file transfer? I didn't find your feedback on github. Thanks! |
I am Currently experiencing a similar issue, my WiFI card supports monitor mode, including ACKnowledgement of Incoming frames but owlink still gives this output (i removed the ascii art):
when i run
|
Wireless controller:
3d:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Owl tell me that:
Could not put device in monitor
But my WiFi card should work as expected:
I successfully put my WiFi adapter in the monitor mode and grab some traffic via tcpdump. Wireshark show me some AWDL packets. I use this guide to check my card.
https://andreas-mausch.de/blog/2018/04/30/wifi-monitor-mode/#intel-dual-band-wireless-ac-8265-iwlwifi
The text was updated successfully, but these errors were encountered: