NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
MLD not working as expected with local link addresses and local list multicast
This might well be a miss understanding of how IPv6 works but I've asked around and other confurmed my thinking. This is in a pure IPv6 setup, I am not using IPv4 (other than the web admin).
1) I...
Hi EricZ,
Sorry for the delay. I've sent the files to switch_support after I factory reset the switch and applied the steps set out in my original post. Still seeing all traffic to C and C never joins the groups.
Output you requested
(M4300-8X8F) #show mldsnooping
Admin Mode..................................... Enable
Multicast Control Frame Count.................. 0
Interfaces Enabled for MLD Snooping............ None
VLANs enabled for MLD snooping................. 300
(M4300-8X8F) #show mldsnooping ssm groups
VLAN Source
ID Group Interface Reporter Filter Mode Source Address List
---- ---------------- --------- ---------------- ----------- -------------------
There are currently no entries in the table.
(M4300-8X8F) #
I've got a the big brother of this switch on my desk as well so will be testing that shortly.
Thanks
I got your tech-support file, thanks!
I notice there is 4 up ports(1,2,7,10), so how abount connection to Host A/B/C.
And you running MLD Snooping on VLAN300, right? And only port(1,2,7) belong VLAN300. So which host is running MLD Server role? and Which host is running MLD Client role?
As in MLD Snooping feature, first the Client will send report packet to join Multicast Group, then the Server will send Multicast stream to different Groups, only the Client has joined the correct Group can receive the Multicast.
Due to there is no any Groups info when you run command 'show mldsnooping ssm groups', so please double chek if the Clients send out report packet to join Groups?
Then on all ports, there is no need to enable 'ipv6 pim'.
Hi EricZ
Port to hosts 1 = A, 2 = B & 7 = C all on VLAN 300. Port 10 is on VLAN 1 and used to admin the switch using the web interface & has nothing to do with the multicast traffic.
Using your terms A & B are Servers and C would be a Client. In the setup I have running on my desk A is sending data to ff02::3000 and B is sending data to ff02::3001, C (had to switch PC's) is now inspecting all packets incoming (on port 7) using TcpDump and is seeing the data from A & B. C has not joined the multicast groups at all. In the multicast model I should not see any multicast traffic on port 7/C unless C has subscribed to the groups but it is.
As an experiment I switched to using static IPv6 addresses and none Link Local scoped multicast groups and I was seeing the same thing.
I didn't enable "ipv6 pim". After the switch was factory reset I ran the Ezsetup (I forget the name of the command but it sets up basic info like whcih address to run the website on). Then logged into the website and configued following the link
I have just tried using a M4300-96X and I get the same issue.
MLD Snooping is used for IPv6 Multicast forwarding. So please make sure the Destination MAC and IP is Multicast range.
For example:
Host A is Server, Host B/C is Client;
1). Host B/C not send report packet to join Groups. then Host A send IPv6 multicast stream(DMAC=33:33:00:00:00:01, DIP=FF1E::1);
In this scenario, Host B/C cannot receive the IPv6 multicast stream due to no any client join the Group;
2). Host B send report packet to join Groups(DIP=FF1E::1, DMAC=33:33:00:00:00:01), then Host A send IPv6 multicast stream(DMAC=33:33:00:00:00:01, DIP=FF1E::1);
In this scenario, only Host B can receive the IPv6 multicast stream, Host C cannot receive any packet. And on switch run command 'show mldsnooping ssm groups' can display Groups member port include Host B.
Hope it helps!
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
