localzuk Posted April 13, 2015 Posted April 13, 2015 I'm trying to get this set up to allow devices on our wireless network to AirPlay Mirror their screens to copies of AirServer installed on laptops. The setup I've got is as such: Wireless VLAN - 7 Wired VLANs where AirServer might be running - 1, 2 and 3. I have enabled Bonjour Gateway on our controller and entered rules as follows: Service: Airplay From VLAN: 1 To VLAN: 7 Service: Airplay From VLAN: 2 To VLAN: 7 Service: Airplay From VLAN: 3 To VLAN: 7 I still can't get the Airplay button to appear on ipads/ipod touches though. If I put one of the laptops directly on the same VLAN, all is well and I can AirPlay Mirror. So I know the software and the iPads/iPods are working fine. Its gotta be the gateway. What am I missing?
localzuk Posted April 13, 2015 Author Posted April 13, 2015 I have also tried a different wireless VLAN (eg. vlan 117). So I have a laptop connected via VLAN 117 and the iPads/iPods via VLAN 7, with a rule for AirPlay From VLAN 117 To VLAN 7. Still no joy.
Michael Posted April 13, 2015 Posted April 13, 2015 It's well known that AirPlay/AirSever/Apple TV - whichever method all needs to be on the same VLAN, irrelevant whether the VLANs can talk or not. This is an Apple design. This is why (as great as it could be) to separate Bonjour traffic with everything else, it generally isn't possible, as in the context of AirServer, this runs as a service on Windows 7/Mac OS X, so you end up having to have everything on the same VLAN anyway!
localzuk Posted April 13, 2015 Author Posted April 13, 2015 Ruckus Bonjour Gateway is supposed to do this job though - its supposed to do the relaying, that's its purpose.
Michael Posted April 13, 2015 Posted April 13, 2015 I'm not 100% sure you're right. A quick Google says Ruckus Bonjour Gateway allows multiple subnets to communicate - no mention of VLANs. Sounds like it's more applicable to a supernet.
localzuk Posted April 13, 2015 Author Posted April 13, 2015 The entire thing asks for VLAN IDs - you specify from VLAN and to VLAN.
White_Fi Posted April 13, 2015 Posted April 13, 2015 Yes you are correct, the ZD will act as an mDNS (bonjour) "proxy" for multiple layer2 subnets/networks what ever you want to call them(VLANs - multiple layer2 networks on the same switch). The ZD will only act as a proxy for the mDNS traffic which is layer 2 so you must ensure that you have layer3 routing between the vlans for the service traffic to work after discovery. The ZD will not route the traffic only make the Layer2 discovery traffic available from 1 VLAN to another. Since the discovery isnt working I suggest you enable the bonjour rule on your ZD bi-directionally. VLAN 7 - 1 and VLAN 1 - 7. Make sure you have the correct apple service as well.
Davit2005 Posted April 13, 2015 Posted April 13, 2015 Does this give any pointers http://a030f85c1e25003d7609-b98377aee968aad08453374eb1df3398.r40.cf2.rackcdn.com/feature-sheets/fs-smartway.pdf
localzuk Posted April 14, 2015 Author Posted April 14, 2015 Yes you are correct, the ZD will act as an mDNS (bonjour) "proxy" for multiple layer2 subnets/networks what ever you want to call them(VLANs - multiple layer2 networks on the same switch). The ZD will only act as a proxy for the mDNS traffic which is layer 2 so you must ensure that you have layer3 routing between the vlans for the service traffic to work after discovery. The ZD will not route the traffic only make the Layer2 discovery traffic available from 1 VLAN to another. Since the discovery isnt working I suggest you enable the bonjour rule on your ZD bi-directionally. VLAN 7 - 1 and VLAN 1 - 7. Make sure you have the correct apple service as well. I've got it all set up as you suggest and still no luck. All inter-vlan traffic is routed at layer 3 already, so all vlans can communicate with each other without issue. I'm trying to get AirPlay mirroring working, so am assuming that the service is AirPlay (would make sense, but hey, this is Apple we're talking about). Question - what is doing the proxying? The APs or the controller? If the latter, does that mean each of the vlans needs to be trunked to it also? As it stands, the only VLAN the controller is on is our server VLAN, untagged.
White_Fi Posted April 14, 2015 Posted April 14, 2015 Ah, thats the issue then. By default the ZD does the mdns proxy so it needs to be aware of the vlans. Get the vlans tagged on the switch ports and you should be ok.
localzuk Posted April 14, 2015 Author Posted April 14, 2015 That's got it. All working now. I have a few very happy trial users now!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now