Skip to content
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

Macbook 2014 with Arch Linux. Can't run OWL #51

Open
tarkh opened this issue Sep 3, 2021 · 2 comments
Open

Macbook 2014 with Arch Linux. Can't run OWL #51

tarkh opened this issue Sep 3, 2021 · 2 comments

Comments

@tarkh
Copy link

tarkh commented Sep 3, 2021

Macbook 2014 with Arch Linux. Can't run OWL with Netlink operation not supported error. Network adapter is BCM4360 802.11ac [14e4:43a0] (rev 03) which works fine in both 2,4 and 5 GHz modes, BT also works ok.

I've discovered on manpage that you CAN enable monitor mode like this:
echo 1 > /proc/brcm_monitor0
(https://wiki.archlinux.org/title/broadcom_wireless#Setting_broadcom-wl_in_monitor_mode)

After this command mew interface prism0 appears in system (with SAME MAC address as BCM4360 interface, usually called wlp2s0), which gives you ability to monitor network. So the question is - how can I tell OWL to use this particular device for monitoring function? Thank you!

Originally posted by @tarkh in #24 (comment)

@db192
Copy link

db192 commented Dec 16, 2021

Dear all,
thanks for the great project!

I have indeed the exact same issue (Macbook Air with BCM4360 [14e4:43a0] running Arch Linux). Enabling monitor mode (see in @tarkh post) creates the prism0 interface which is listed as well by iwconfig and works fine for other applications, eg. wireshark. However, trying tell owl to use that device via sudo owl -i prism0 fails Error while receiving via netlink: No such device. I guess I will have to tell owl somehow to use my actual wifi card wlan0 and prism0 just for monitoring. @schmittner suggests in his comment that this is somehow possible:

A (hacky) idea that I have not tested: You could add a second virtual interface via iw and then set one of the interfaces to monitor mode (for owl) and the other in a "regular" mode, e.g, ad hoc configured with the same BSSID as AWDL. If you run both modes in parallel (probably again depends on driver), the second (ad hoc) interface would have to ACK all incoming frames.

Originally posted by @schmittner in #9 (comment)

Could anyone help me out there? I would really appreciate this, since being able to airdrop on Linux would significantly improve my workflow!

Thanks again and all the best
David

@midozalouk
Copy link

I think you should use - N
Awl will work
But I have no luck to run opendrop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants