Hi.
I understand the latest releases of RouterOS has support for IGMP Snooping. I can’t find it in webgui or winbox however. So what is the command for turning it on?
Thanks.
Hello, the use of RouterOS IGMP Snooping is described here:
https://wiki.mikrotik.com/wiki/Manual:Interface/Bridge#IGMP_Snooping
Thank you, just what I was looking for.
One followup, it seems I have to run OS 6.41RC for the IGMP snooping. I am currently running 6.40.1 Current. Are there any problems related to upgrading? Will I lose my config?
Edit: I found the answer elsewhere. Upgraded the router and configured IGMP Snooping. Everything went smooth with no hickups, and the function seems to work exactly like planned.
IGMP snooping is the only reason we are still buying Cisco switches. If this works, our Cisco rep will lose an account now..
I am no expert, but it most definitely works with my IPTV. Before this was enabled, I could see the IPTV Multicast traffic on all ports. Now, with IGMP Snooping enabled, only the correct ports receive the traffic.
Well, IGMP flooding over WiFi is still here. I have a hAP lite with RouterOS 6.41 and even after enabling IGMP snooping on bridge interface I have IGMP traffic on all connected wireless devices.
This may be a silly question, but are any wireless devices subscribed to the multicast group? Furthermore, I’m not sure whether IGMP traffic itself should be getting filtered, or just the actual multicast data itself. IGMP is just the protocol that devices use to join/leave multicast groups. If your wireless network has a multicast router / source attached to it, then IGMP would need to get forwarded so that the router/source can know when listeners join their groups, so I would think that IGMP should be forwarded even with snooping.
As for the multicast traffic itself - if any wireless device is actually subscribed to a multicast group, then the wap must broadcast it to all clients. I mean, it’s not like the AP can prevent the signal from physically reaching wireless devices which aren’t joined to the multicast group.
Sorry, of course I mean multicast traffic. I need IPTV from my ISP to work on a notebook over WiFi. The problem now is: when any device connected to my hAP lite via WiFi start viewing IPTV, all other wifi-clients start receiving multicast traffic simultaneously. IGMP snooping enabled/disabled on bridge interface dosn’t has any effect. In the meantime my other router, TP-LINK TL-WR841N, doesn’t has this problem. Is it a bug or I do something wrong?
Well, I’m not sure if Mikrotik has this feature or where I saw it in other gear (I think it was Aruba) but some 802.11 gear has a feature where multicast traffic is converted into unicast and sent only to the one client. Otherwise, it is simply broadcast as multicast. When sending as multicast/broadcast, the AP must use the lowest common speed between the stations in order to guarantee that everyone will receive the transmission error-free.
In reality, ALL wireless transmissions are broadcasts, right? Even if the other devices aren’t joined to the multicast group, the transmission is broadcast by the WAP’s antenna and reaches all devices, right? The only real difference in this case would be that if your AP isn’t doing the unicast conversion, then the speed is going to most likely be at a much lower “group” rate. I don’t think that the other clients’ seeing the traffic is really changing much outside of this detail, because the radio waves are going to be hitting them anyway, whether they bother to record the transmission only to discover that it’s a multicast frame on a group they haven’t joined.
Now I understand better, thank you. But isn’t “multicast helper=full” feature in wireless interface should do exactly this - convert multicast packets from ISP (outside router) to unicast and send it over wifi with max available rate to specific client? (https://wiki.mikrotik.com/wiki/Manual:Interface/Wireless#General_interface_properties) I have it enabled and still see ISP multicast traffic on all wifi clients.
I read the manual page you linked to. By my reading, it’s entirely possible that the multicast helper acts in a manner similar to PIM in dense mode - i.e. it sends a copy to EACH client at its individual mod rate, as opposed to sending a copy only to the subscribed stations. Given that they just now implemented IGMP snooping, this could be possible. Do bear in mind that converting to unicast will greatly multiply the bandwidth consumed on the AP, especially if you have lots of devices on it.
Hello.
What version of IGMP protocol (v1, v2, v3) IGMP snooping feature in CRS should work with?
There is no such information in wiki-doc about crs3xx.
It looks like igmp-snooping=yes doesn’t function at least with IGMPv3. Devices are unable to receive traffic of multicast groups when connected to crs326.
/interface bridge
add admin-mac=CC:2D:E0:02:2E:1C auto-mac=no igmp-snooping=yes name=bridge1 protocol-mode=none pvid=611 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 ingress-filtering=yes interface=ether1 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether2 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether3 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether4 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether5 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether6 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether7 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether8 pvid=199
add bridge=bridge1 ingress-filtering=yes interface=ether9 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether10 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether11 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether12 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether13 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether14 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether15 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether16 pvid=611
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether17
add bridge=bridge1 ingress-filtering=yes interface=ether18 pvid=611
add bridge=bridge1 ingress-filtering=yes interface=ether19 pvid=611
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether20
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether21
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether22
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether23
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=ether24
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=sfp-sfpplus1
add bridge=bridge1 frame-types=admit-only-vlan-tagged ingress-filtering=yes interface=sfp-sfpplus2
/interface bridge vlan
add bridge=bridge1 tagged=ether17,ether20,ether21,ether22,ether23,ether24,sfp-sfpplus1,sfp-sfpplus2 \
untagged=\
ether1,ether2,ether3,ether4,ether5,ether6,ether7,ether9,ether10,ether11,ether12,ether13,ether14,ether15,ether16,ether18,ether19 \
vlan-ids=611
add bridge=bridge1 tagged="ether1,ether2,ether3,ether4,ether5,ether6,ether7,ether8,ether9,ether10,ether11,ether12,ethe\
r13,ether14,ether15,ether16,ether17,ether18,ether19,ether20,ether21,ether22,ether23,ether24,sfp-sfpplus1,sfp-sfpplus2" vlan-ids=610
add bridge=bridge1 tagged=ether18,ether24 vlan-ids=161
add bridge=bridge1 tagged=ether16,ether17,ether19,ether24 untagged=ether8 vlan-ids=199
add bridge=bridge1 tagged=ether19,ether24 vlan-ids=708
add bridge=bridge1 tagged=ether22,ether24 vlan-ids=715
add bridge=bridge1 tagged=ether17,ether19,ether24 vlan-ids=843
add bridge=bridge1 tagged=ether20,ether24 vlan-ids=844
add bridge=bridge1 tagged=ether17,ether18,ether19,ether20,ether21,ether22,ether24 vlan-ids=852
add bridge=bridge1 tagged=ether18,ether24 vlan-ids=1184
UPD: IGMPv2 also doesn’t work with igmp-snooping on crs326. So by the fact there is no IGMP snooping on crs. Very sad…