owl

An implementation of AWDL on Linux requires a Wi-Fi card that supports "active monitor mode with frame injection". [1] I looked into using it with an Intel Wi-Fi card I had and it appeared mine wasn't supported. I'm guessing the situation is similar on Android in terms of SoC support. [1]: https://github.com/seemoo-lab/owl?tab=readme-ov-file#require...

"you will need a Wi-Fi card supporting active monitor mode with frame injection" https://github.com/seemoo-lab/owl

In general, rigidity of stack is a malfeasance. Over protecting the user brings fragility, un-adaptability, that curses the world. Android certainly is a rigid narrow protective stack that refuses to accommodate, again and again. Different genre, but decades latter and it still won't work on many ipv6 networks because for no clearly stated reason it won't support DHCPv6: Android is full of these weirdly unstated "principled" anti-compatibilities, and I can't excuse blaming the devices or networks for being what they are: it's the unbending rigid OS that offends me. I do rather hope perhaps perhaps perhaps the EU & DMA or other may perhaps bend Apple off their rotten course of making non-standard bespoke systems. It seems like very recently the EU is getting ready to cave & abandon all their demands for trying to use standards, that their

The AWDL part is in C: https://github.com/seemoo-lab/owl

The article links to a Linux implementation that does it with off the shelf WiFi hardware. You do need specific features in the hardware/firmware, but there are consumer devices that have that e.g. Atheros AR9280. https://github.com/seemoo-lab/owl It currently drops connections to an AP, but the authors of the implementation seem to believe this could be fixed: > OWL does not allow a concurrent connection to an AP. This means, that when started, the Wi-Fi interface exclusively uses AWDL. To work around this, OWL could create a new monitor interface (instead of making the Wi-Fi interface one) and adjust its channel sequence to include the channel of the AP network.

> Wi-Fi NAN I have been very interested in this. Sadly, finding hardware that supports it (both HW and SW) seems quite hard at the moment. This stackoverflow answer mentions a few, but I have no idea about software support: https://stackoverflow.com/a/54214808/3795597 I tried poking around the Linux drivers and userspace tools (which required reading some source code, the documentation is pretty bad), I summed up some of my finding there: https://superuser.com/a/1786039 So far, I only encountered two phone series that supported NAN: POCO and Google Pixel. So much for interoperability. I still wonder if it's possible to build a compatible implementation leveraging Monitor mode. This is how Owl (open source "Airdrop"/ADWL implementation) does it: https://github.com/seemoo-lab/owl

"it is unlikely that a non-Apple device has hardware support for adhoc wireless connections between devices. This makes implementation of AirDrop directly on non-Apple devices practically impossible without additional hardware. Instead we’ll implement a proxy..." I get what they mean here, but it has been done. It does require a Wi-Fi card with support for monitor mode and frame injection. OWL did it with an Atheros AR9280. Open drop also requires extracting keys from an Apple device if you want Apple interop. See OWL: https://github.com/seemoo-lab/owl And Open drop: https://github.com/seemoo-lab/opendrop