From 1972585725c8031754d8e8e24c505e9738d45277 Mon Sep 17 00:00:00 2001 From: Neil Alexander Date: Mon, 19 Aug 2019 22:42:00 +0100 Subject: [PATCH] Update 2019-08-19-awdl.md --- _posts/2019-08-19-awdl.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/_posts/2019-08-19-awdl.md b/_posts/2019-08-19-awdl.md index 37b2ef2..327c169 100644 --- a/_posts/2019-08-19-awdl.md +++ b/_posts/2019-08-19-awdl.md @@ -103,9 +103,9 @@ From a user perspective, the `awdl0` interface looks entirely unremarkable. It behaves largely like any other ethernet interface, carrying regular IPv6 traffic. In the background it's a bit more complicated, as the AWDL driver performs traffic filtering for security reasons, namely, to stop someone sat -next to you in the airport from browsing your file shares. Namely, regular -listening sockets won't accept connections over AWDL unless a specific socket -option was configured on the socket before it started listening. +next to you in the airport from browsing your file shares. Regular listening +sockets won't accept connections over AWDL unless a specific socket option was +configured on the socket before it started listening. Multicast traffic, however, does largely get passed through the filter untouched. Bingo.