Ruckus - Airplay - Bonjour Gateway

[Sale_El]

Problem: unable to connect Apple TV and ipad over vlans unless they are both on the same vlan as the AP's

 

The network:

Ruckus ZD 3000 Version 9.8.0.0 Build 373 plugged into core.

Vlan 1 - (main scope 10.18.144.x /22)

Vlan 5 - (visitor wifi 172.17.12.x /24)

Vlan 10 -(BYOD wifi 172.17.32.x /20)

Apple TV

ipad

 

AP's and ZD are on Vlan 1 but pushing out the vlans based on SSID. when apple TV is on vlan 1 and ipad is on vlan 1 airplay works. problem is this causes authentication with our smoothwall to be an issue, so no one can get on the web. Tried ipad on vlan 5 and ATV on 1 this caused ipad to not show the airplay icon. configured Bonjor gateway on the ZD to see airplay traffic from vlan 1 - 5 and vice versa... did it from the ZD and when that failed did it from the AP one and that didnt work either. Finally, connected the ATV to vlan 5 and the ipad to vlan 5 and i am still unable to see the airplay icon.

 

Is there something i am doing wrong, it is very strange when they are both on the same network but still unable to see the multicast packets.

 

Any help greatly appreciated.

 

Sal

[mdrabble]

Looking at the way you have described thing it should work.

 

Have you got the VLan tagging correct on those ports?

[FN-GM]

Just as a note you should never ever use vlan 1. When traffic goes between switches on trunk it applies a temporary "header" to the packet so it knows what VLAN it has come from. So when it reaches the other switch, that switch knows what vlan to put the packet into. This happens on all VLANs apart from VLAN 1, the switch does not apply a header for traffic coming from VLAN 1. This means with a bit of software people can apply there own header and send the packets to another VLAN. This means the traffic can be sent to secure VLANs bypassing security (such as ACL's etc) you have in place.

 

I would discontinue the use of VLAN 1 and use any other number. The other option is to change the native VLAN on your trunks to another and don't use that new VLAN. But this can cause all sorts of problems when trunking between devices.

Edited October 16, 2014 by FN-GM

[Sale_El]

They way ive set it up is all the vlans are tagged on the AP ports and untagged on vlan 1 all trunks are set correctly

@FN-GM i am aware of the issues and i have only recently inherited the site, until now the whole network was running on a flat vlan 1! Thanks for making me aware i still have a lot more work to do ;-)

[White_Fi]

OP: As mdrabble has stated; have you got the VLAN tagging correct?

 

When doing BJGW on the ZD the ZD needs to be able to throw traffic into those VLANs. i.e the switch port the ZD uses must be a Trunk port with the relevant VLANs tagged.

This will allow the ZD to proxy the MCast traffic (which is Layer2) it will not, however, route the traffic once the discovery between devices has been established.

The VLANs Gateway or other Layer3 device will do the routing between the VLANs.

 

The second part is that when both devices are in VLAN5 you are still unable to to discover via mDNS... Is there anything dropping multicast packets in this subnet?

There is a setting on the ZD to drop MCast traffic on WLANs.. My guess if there is nothing else dropping the MCast traffic then you have that enabled under the WLANs (VLAN5 WLAN) advanced settings.

[jtotheb]

Just to double check, can you route between the VLANs? If not, one factor could be that you will need to be able to route between them for it to work.

[White_Fi]

Just to double check, can you route between the VLANs? If not, one factor could be that you will need to be able to route between them for it to work.

 

This is true but discovery would still work as mDNS is Layer2 and the ZD will be forwarding that request. It would stop working at that point should no Layer3 routing be available.

The first place to check would be the correct VLAN tagging and configuration on the ZD such as BJGW enable/ setup and that the WLAN is not dropping MCast traffic.

[Sale_El]

the ZD goes into our core, the access link is tagged on all wireless vlans and untagged on vlan 1 (same as AP's) core fibres all trunked on wireless vlans so the core does all the routing between the vlans.

 

I have checked that setting and it is not ticked. i don't know what else would drop the packets, all our AP's go into HP switches that are connected via fibre to the HP core which in turn is connected to the ZD

 

thanks for the replies

[Marshall_IT]

I had issues when I set up the bjgw in both directions.

 

You only need to set it in one direction, so from the vlan with the Apple TV on it to the iPad vlan.

[Sale_El]

currently ATV is on VLAN 5 and ipay on 1 and the ruckus rule is attached.

[White_Fi]

Have you tried reversing the Rule, so from 1 to 5? It would seem you need the iPad (VLAN 1) as the from VLAN and ATV (VLAN 5) as the to VLAN