-
Notifications
You must be signed in to change notification settings - Fork 271
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
Has this worked for anyone recently? #96
Comments
it does work even with latest IOS 16 |
What WiFi module has you used that has worked for you? |
thanks to the people who came up with the "short list": https://github.com/morrownr/USB-WiFi/blob/main/home/The_Short_List.md These device support active monitoring I'm using the first one in the list, which is available and can bought easily |
Thanks, that's really helpful. Do you know of any recent success using the Nexmon patches on a raspberry pi zero w 1.1? Also, do you know if a the wifi module will work if it doesn't have 5g band access? (Sorry if that's a dumb question) |
I'm not sure about nexamon, tried it a bit with PI 4, then switched to proper wifi module. Not sure I had other issues or it was not working at all I'm only using Channel 6 with Owl, AWDL works on 3 channels, for me the only stable one is 6 which the default anyway. Owl does not support channel switching as far as I know, so with channel 6, only 2.4GHz |
Thanks so much for this; I'll keep trying with the Raspberry Pi Zero W 1.1. In the meantime, if anyone else has any successes to relay, on any hardware, it would be great if you commented with them. |
I've uploaded a full all in one soltuion: |
Thanks! |
Reopened so that this post is more visible in issues. Let me know if this is faux pas in GitHub etiquette. |
I have heard from @TheLastGimbus in TheLastGimbus/easydrop#2 and #79 that Apple has made changes that prevent Opendrop from interfacing with current devices. Is this true? Has Opendrop worked for anyone for current versions of iOS? On any platform and on any hardware.
The text was updated successfully, but these errors were encountered: