And I have no traffic allowed from IoT vlan to the main vlan. Somehow google discoveres them automagically. It just works without needing anything special. Now bear in mind that my phone being in the main vlan doesn't really need anything special to discover all my google devices. Where eth0 is my main vlan and eth0.9 is vlan id 9 for IoT devices. Pretty neat stuff.Ĭode: Select all udp-broadcast-relay-redux -id 1 -port 5353 -dev eth0 -dev eth0.9 -multicast 224.0.0.251 -s 1.1.1.1 -f This lets you keep your AppleTV's on a wired, segregated network while allowing conference room guests to AirPlay to the ATV in that specific conference room. I settled for setting up a trunk port on my CRS and attaching a Raspberry Pi with an interface for every VLAN running avahi.Ĭisco and Aruba have some very interesting mDNS routing capabilities where they can selectively allow mDNS services to work between subnets based on physical location (associated WAP). I think an mDNS reflector might be an interesting feature to have if for no other reason than to help people avoid building these ungodly bridged network monstrosities just for IOT support. (See the Linux/avahi portion of this link for an example) I think the most available solution for ROS users at the moment is to launch a Metarouter with avahi installed on it and configured as a reflector. Perhaps some interesting nat/mangle gymnastics are possible. Well, I did a bit of reading and see where the problem is (mDNS using link-local-only multicast group) so obviously routing won't fix the issue. Obviously this doesn't cause the Mikrotik to participate in mDNS, but if you want multicast routing, it is available. (switches w/o IGMP snooping just treat multicast as broadcast, so it works, but can bog down a network with unwanted bandwidth) NOTE that this is ROUTING, and not the much-demanded-by-users / much-poo-pooed-by-Mikrotik feature known as IGMP snooping, which is the piece of the multicasting pie that filters multicast traffic off of switch ports which aren't subscribed to it. This is how you enable multicast routing.

You should see both IGMP Proxy and PIM configurations in the /routing menu. Reboot and the package should be available. If not, then you'll need to download the 'extra packages' ZIP for your current model and version of ROS, and copy the multicast package onto the Mikrotik's file system (just drag and drop it using Winbox, for example). It's just not in an obvious location / possibly disabled by default in your router.Ĭheck /system packages and make sure that multicast is installed and enabled. I'm not sure about the IOT stuff (personally shy away from such - they're usually great-big-grand-canyon-sized security flaws that are often the subject of blackhat talks at DefCon, etc) but I can say that Mikrotik DOES support multicast routing.

Wiki reflector 2 airplay