A Windows machine running IPv6 automatically joins several multicast groups when connected to a network. This demonstration uses Wireshark and the netsh command to capture and examine those multicast memberships in real time.
IPv6 Multicast on Windows
We're going to take a look at a Windows machine and see what multicast memberships it subscribes to, because it has IP version 6 running on its interface.
I'm on my demo laptop right here, and what I'm going to do is turn on Wireshark to monitor the ethernet interface, and then I'm going to plug it into the switch, and we are going to see what memberships it becomes a part of, and what information is in those packets that are sent out, the frames that are sent out to become part of that membership.
Here I have Wireshark up. I'm going to double click my ethernet connection. Notice there's nothing coming across it right now, because it's not plugged in. So I'm going to plug this in and then we'll see what traffic comes across it.
Now that we've plugged in this device, I've stopped the capture. We've got a lot of data now of what traffic goes across this interface when you plug it in. What I'm going to do is sort by protocol, and what I'm looking for are the ICMP version 6 packets that are in here.
I look at these and I see some multicast listener report messages. So I look in here and we see something specific: this is a colon 14. So this is the multicast address associated with the IP address that we assigned to this device, the static IP address. I click on this one — same thing we've got there. So we can see that it subscribes to some of these multicast addresses in here.
What I can do is pull up a command prompt and type in netsh interface ipv6 show joins. This is a command that we've used before to take a look at what multicast addresses it's joined to.
I can see here is the ethernet interface. I'll move this down here towards the bottom so we can see some of the list, and as I scroll through these we can see that ff02::fb is on that list down there, and same thing with ff02::c. So it's subscribing to these different lists out there, these different memberships, multicast memberships.
Some of the ones that it subscribes to: we've got this ff02::1:ff00:14. That's the solicited node multicast group that's associated with the static IP address that we assigned to it. And then we also see this ff02::1:ffd7:34fa. That's associated with the link local address that we had on this, so that's the solicited node multicast address associated with the link local.
Just to verify that — it ends in 34fa — I can type in here ipconfig and scroll to our ethernet, and here's the link local, and it ends in 34fa. So yes, we see that this is the link local address. It's created a solicited node multicast address, and then it's registered that solicited node multicast address so that it can receive messages that are destined for that multicast address.
So there you have it. That's part of the process of this: it creates that solicited node multicast address, and then it registers that to be part of that multicast membership.
TechKnowSurge builds IT and cybersecurity professionals through hands-on, concept-first training built around real understanding — not memorization. Free interactive tools, structured programs, and 25+ years of real-world experience, all in one place.
Explore free tools and programs →