Hi Mikrotik community! I am playing around with replacing my home lab setup with all Mikrotik. Right now I am using a Fortinet stack that was gifted to me. It is awesome, but I get bored and want to try something new… anyhow, right to the point.
In my home lab I use 3 VLANs. My TVs and AppleTV, multifunction printer and such are on VLAN 5, my wife and I are on VLAN 10, and my kids are on VLAN 15. We use airprint to our printer, and our phones to control the AppleTV. Both of those features use multicast. Right now I have no problem with the Fortinet stack routing that multicast traffic between VLANs. I dabbled briefly in this before with Mikrotik and got stumped. I am not using Mikrotik wireless access points at this time. Not sure if that detail helps, but incase it does, there you go!
So my specific question: I want multicast traffic to be able to flow between my TV VLAN (vlan 5), and my “parents” vlan (VLAN 10). Can someone help me understand the right want to do that on Mikrotik?
Not being a huge fan of bridging bonjour as it creates a point where a router could be injected it’s actually possible to use the Apple associated services via DNS directly in a way that isn’t tied to leaking an intentionally link-local discovery protocol throughout your wan. That said the RouterOS DNS server is lacking the features to implement it.
Isn’t the whole point of Bonjour/ZeroConf discovery supposed to be DNS independent?
For example, the HDHomeRun TV tuner discovery requires the EyeTV application to probe and listen on the same subnet. How would DNS records address this issue across VLANs?
It’s not that you can use a DNS to make Bonjour work, it’s that you can use a DNS as a next-best option to compensate for the fact that Bonjour doesn’t work.
They’re never going to see those broadcasts. The mechanics of why have been previously posted. Bonjour will not work on remote access connections without active server assistance.
If you absolutely need Bonjour to work, you’ll have to obtain the avahi server, invest in a Linux device to run it, and configure it to your taste.
.
That was my understanding too, but @idlemind said:
it’s actually possible to use the Apple associated services via DNS directly in a way that isn’t tied to leaking an intentionally link-local discovery protocol throughout your wan.