topic Re: Ruckus AP mDNS Query "_communicator._tcp.local"? in Access Points - Indoor and Outdoor

Ruckus AP mDNS Query "_communicator._tcp.local"?

Greg_WiGuy — Wed, 16 Oct 2019 14:34:48 GMT

While doing some packet analysis to define all the required ACL rules for Ruckus APs, I came across this curious query a new AP out of the box sends out before discovering our SZ. Can anyone explain what this query is looking for, and if it's necessary to allow?

Thanks!

Re: Ruckus AP mDNS Query "_communicator._tcp.local"?

albert_pierson — Wed, 16 Oct 2019 14:51:35 GMT

Hi WiGuy,

This mDNS query is sent by AP to permit it to auto discover SZ100 or vSZ-E (enterprise) controllers that are on the same L2 (VLAN) as the AP. This makes installation of a SZ100 or vSZ-E network in a simple single management network seamless and automatic.

It is only needed to be permitted in the L2 network where AP's and SZ are connected if auto discovery is required. mDNS is a layter 2 protocol which normally does not cross L3 boundaries.

I hope this answers your question,

Thanks for choosing Ruckus Networks products - a Commscope company.

Re: Ruckus AP mDNS Query "_communicator._tcp.local"?

Greg_WiGuy — Wed, 16 Oct 2019 15:01:04 GMT

Thanks Albert - looks like it won't be needed in our deployment.