From 55e9a57ae365e1e2a47bee5f736743173ce2fda3 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Thu, 29 Jan 2026 21:10:44 +0000
Subject: [PATCH] doc: update Windows device discovery documentation

Infix now advertises _workstation._tcp, making devices appear
automatically in Windows Explorer's Network folder (Win 10 1709+).
Lead with this, show .local hostname usage for ping/SSH, and demote
the IPv6 multicast ping caveat to a note.

[skip ci]

Signed-off-by: Joachim Wiberg <troglobit@gmail.com>
---
 doc/discovery.md | 23 +++++++++++++++++++++++
 1 file changed, 23 insertions(+)

diff --git a/doc/discovery.md b/doc/discovery.md
index 06e7e165..aa5fd8d7 100644
--- a/doc/discovery.md
+++ b/doc/discovery.md
@@ -43,6 +43,29 @@ admin@fe80::ff:fec0:ffed%tap0's password: admin
 admin@infix-c0-ff-ee:~$ 
 ```
 
+### Windows
+
+Infix advertises a `_workstation._tcp` DNS-SD record alongside its other
+mDNS services.  Windows 10 (build 1709+) and Windows 11 recognise this
+record and show the device in **File Explorer → Network** automatically —
+no extra software required.
+
+From the command line, use the `.local` hostname directly:
+
+```cmd
+C:\> ping infix-c0-ff-ee.local
+C:\> ssh admin@infix-c0-ff-ee.local
+```
+
+> [!NOTE]
+> IPv6 multicast ping (`ping ff02::1%if1`) may not display responses on
+> Windows even though the Infix device replies correctly.  If you need to
+> confirm connectivity, Wireshark will show the ICMPv6 echo replies
+> arriving.  Use mDNS (see [mDNS-SD](#mdns-sd) below) as the reliable
+> alternative.
+
+![Wireshark showing IPv6 ping responses](https://github.com/addiva-elektronik/alder/assets/122900029/c45d7726-448f-4c30-878e-bcf976dff531)
+
 
 ## LLDP