Hello, what exactly was done to send back the tunnel-password? I've run into the same issue your having. Thanks ... View more

The server doesn't have to join any group.  You'll have to verify to what group the server is sending the streams.  Just perform a packet capture on the link to the server and limit your capture by following capture filter: net 224.0.0.0/4.   So you can identify what streams are actually being transmitted from the server. Then you'll have to perform capture on several points (transit) and destination network 10.11.100.0/24.  To see if your packets reach it L3 wise. Finally check if they receive them on the speaker ports.   For the receiving devices that are on the same VLAN as your server should work no problem because since you enabled PIM on 10.10.100.0/24 the IGMP querier function should also work.  And even in the odd case it didn't it would flood the multicast to all ports unless you disabled that feature of course. ... View more

The only way to do this in Meraki is with ACL's. That said, they're pretty simple to setup.   Depending on what works best for your scenario you can apply them via SSID, Vlan, Group Policy.   The below doc might be a useful reference https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Configuring_Simple_Guest_and_Internal_Wireless_Networks ... View more

@mcbrown a few answers:   The gateway should just be on any other device, not that one.  Our devices may have another switch or two, before they get to the gateway. I'll leave that for someone else One combined network per site/building, you get the best visibility that way as 2 It depends on your traffic routes.  In general, if traffic on a switch is predominantly heading to devices on another switch, do the routing there, if traffic is staying local to the switch but across VLANs, route on the local switch.  Obviously the larger your network gets the more grey these decisions become. ... View more