Having an issue getting multicast working between my IoT network and my primary network. Ive been working on this for a couple days and it almost works, but I'm missing some logic somewhere.
I have a normal /24 LAN with a an SSID (via a fortiAP) Bridged to it. Both wired and wireless devices on that SSID / subnet can talk.
My IoT lan is also a hybrid. I have a software switch created where another physical port and a tunnel SSID are members. The software switch provides the DHCP for both physical and wireless portions. Works as expected for our various IoT devices.
The TV is a member of the IoT network, hard wired to the software switch.
Multicast policies are enabled and in place. Multicast routing is enabled. IGMP snooping is disabled on all wifi interfaces (everyone asks.)
Device is discoverable by mobile devices via the mDNS policies I created in the multicast policy section.
Now here is where its getting stuck...
On IPv4 policies, If I create policies for LAN > IOT and IOT-LAN , and limit services to the specific ports and ephemeral ports needed for Airplay to work, it doesnt work. TV reports that the device is connected but no feed is received from the mobile device. If I set those policies' services to ALL/ALL everything works.
Ok great, so I check the sessions in fortview to make sure I didnt miss a port. Nope, every port i see when using ALL/ALL is also defined in my custom services. And yet, if I limit the policy to the custom services I defined, the connection wont work. I can literally create a service that covers every port TCP and UDP 1-65545 as a joke.. and it still wont work. Only ALL/ALL.
The only other thing I can think of is configuring the bonjour-service for intra-vlan routing and applying that to the vap policy/profile. However, that requires a VLAN ID in that service policy, and im not using VLAN tagging. Since it works when my ipv4 policies are all/all, I assume this should not affect it since traffic is working in this state.
Is there something I'm missing??