IPv6 ping ff02::1 in Windows

[troglobit]

IPv6 ping for link-local mcast addresses such as "ping ff02::1%iface" does not work in Windows.

• Ping goes out, and Infix switch responds ...
• ... but the response is lost somewhere in Windows

Perhaps a firewall issue in Windows.

Links

hints about the following links (reverse direction and old but may be of interest):

• https://superuser.com/questions/490092/windows-doesnt-respond-to-ipv6-multicast-ping
• https://serverless.industries/2019/05/30/find-device-ipv6-link-local.en.html
• https://samsclass.info/ipv6/proj/proj-PingScan-Win.html
• https://medium.com/@netscylla/hacking-ipv6-from-windows-ca23a9602ce7

[troglobit]

Notes 2024-06-12 (J-O)

I tried the proposals in the first link, but without succeeding get ping responses at command line (on wireshark, though, that that was no news).

• first I could not see which profile I had, so I enabled discovery on public and dmain too.
• then I got help from Ejub. I disabled all other interfaces except for the connection to the switch. I could then see I had the public profile. Then I first enabled discovery and sharing for the public profile, but still no ping response. I also changed the profile to private via powershell, and again, no ping response.

I ran into another link which may be of interest. On the other hand, LLMNR seems to do what we solve with mDNS, and does not solve the lack of response to ping ff02::1. I do not think our switches respond to LLMNR. But then comes the mDNS does the trick.

My conclusion is that we are back to recommending use of mDNS by ping/ssh/http to switch.local (or switch-c0-ff-ee.local). ping ff02::1 works, if used together with wireshark. A bit cumbersome. :-/