site_archiver@lists.apple.com Delivered-To: macnetworkprog@lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=natserv.onmicrosoft.com; s=selector1-neilalexander-eu; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=abAau2pFZ43NwvXhNH9A3hWEiLnW8xnyFjSO3LeEQEA=; b=EfQf2AQZu1PgfAKTqL4ObzELoKQpvDtIG/H4A/fKBo4Wyguqqzga4rxTn3mhVfo4meVwNmNmF58YvFDtZVDIrEURB4nIMajvxaH4x0QIjC6CjWpj62wFltRNqn8+lyV4tNlUbknxSpJ8IXOYAPDxDKe12p50CPDmWM+8PJm8Sjk= Thread-index: AQHUyr1+oJAAtxGCKkSraYR9rdoaGaXr9S+AgAACYICAABCngIAAARQ7gAABrwCAAAUP64AAERGAgAAO9Nk= Thread-topic: Waking up AWDL I’m trying to use AWDL on Macs specifically to avoid the requirement for devices to be on the same infrastructure network. :-) Other platforms are limited currently to being on the same network, which may change in the future with Wi-Fi Aware or something, but Apple devices can overcome this limitation and do true peer-to-peer connectivity. That’s what I’m trying to take advantage of. Sent from my iPhone
On 22 Feb 2019, at 18:20, Jens Alfke <jens@mooseyard.com> wrote:
Right, but why do you need to use AWDL?
My understanding, which may be wrong, is that you want to use it to enable infrastructure Wi-Fi connections, which is a great feature. But without platform-specific code, it should still work, right? It’s just that the machines/devices will have to be on the same LAN to communicate directly with each other. (Which doesn’t seem like much of a limitation for Macs; more so for iPhones.)
Do not post admin requests to the list. They will be ignored. Macnetworkprog mailing list (Macnetworkprog@lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/macnetworkprog/site_archiver%40lists... This email sent to site_archiver@lists.apple.com