From 0f0a09fb28d9136a3fc0f0e4e0c0d2a04057a69f Mon Sep 17 00:00:00 2001 From: jokob-sk Date: Tue, 3 Feb 2026 21:04:56 +1100 Subject: [PATCH] DOCS: WiFi extenders and ping vs arp-scan clarification Signed-off-by: jokob-sk --- docs/REMOTE_NETWORKS.md | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-) diff --git a/docs/REMOTE_NETWORKS.md b/docs/REMOTE_NETWORKS.md index 1fda6f17..8ff4848c 100755 --- a/docs/REMOTE_NETWORKS.md +++ b/docs/REMOTE_NETWORKS.md @@ -13,9 +13,17 @@ The following network setups might make some devices undetectable with `ARPSCAN` ### Wi-Fi Extenders -Wi-Fi extenders typically create a separate network or subnet, which can prevent network scanning tools like `arp-scan` from detecting devices behind the extender. +Wi-Fi extenders often **block or proxy Layer-2 broadcast traffic**, which can prevent network scanning tools like `arp-scan` from detecting devices behind the extender. This can happen **even when the extender uses the same SSID and the same IP subnet** as the main network. -> **Possible workaround**: Scan the specific subnet that the extender uses, if it is separate from the main network. +Please note that being able to `ping` a device does **not** mean it is discoverable via `arp-scan`. + +* `arp-scan` relies on **Layer 2 (ARP broadcast)** +* ICMP (`ping`) operates at **Layer 3 (routed traffic)** + +That’s why devices behind extenders may respond to ping but remain undiscoverable via `arp-scan`. + +> **Possible workaround**: +> If the extender uses a separate subnet, scan that subnet directly. Otherwise, use DHCP-based discovery plugins or router integration instead of ARP. See the **Other Workarounds** section below for more details. ### VPNs