Describe the bug
The intent of Avahi/ZeroConf/mDNS is to allow quick discovery and provisioning of devices especially when isolated. Many corporate networks will filter unknown MACs and thus devices will not get an IPv4 assignment without going through bureaucracy. Avahi/mDNS will allow devices to use the SLAAC/LinkLocal IPv6 address for communication otherwise.

To Reproduce
Steps to reproduce the behavior, like:

1. Plug PiKVM directly into Windows Ethernet (without a router providing DHCPv4 assignments)
2. Note that Windows will assign a IPv4 APIPA/LinkLocal address and the fe80:: IPv6 SLAAC LinkLocal address.
3. Open Command Prompt
4. ping PiKVM.local
5. fails
   Expected behavior
   From Wireshark, a mDNS query broadcast from the Windows machine (happens)
   From the PiKVM, a mDNS response to resolve the fe80::XXXX address for browser/ssh access.

Screenshots
Did not capture screen shot

Desktop (please complete the following information):

• OS: Windows 11
• Browser Edge
• Version 149.0.4022.69 (Official build) (64-bit)
• VNC client N/A
  PiKVM info:
• Raspberry Pi board version : RPi 4
• PiKVM platform : N/A
• Video capture type N/A
• KVMD version: N/A
• uStreamer version: N/A
• Linux kernel: Linux pikvm 6.12.93-1-rpi Allow For control of Multiple Hosts #1 SMP PREEMPT Tue Jun 16 23:05:35 UTC 2026 aarch64 GNU/Linux

Additional context
Fresh out of the box