Issue browsing Bonjour services when using Bonjour Gateway on APs

  • 1
  • Question
  • Updated 3 years ago
We're running HMOL 6.5r1 using about 90 AP230s running 6.4r1d.2111

I'm trying to use the Bonjour Gateway to advertise chromecast and airplay mdns entries advertised by Reflector 2 ( on our classroom teacher PCs.

We have one subnet for AP management that is global across site and 4 vlans for wireless access allocated by policy which are global across site. Each different building then has it's own desktop subnet. There is only this one device acting as the Bonjour Gateway at the "centre" of this network, I've configured it like this as all of the APs are on the same subnet it appears there can only be one BDD active. I've changed the Bonjour Gateway priority to 100 and trunked all of the desktop vlans, the AP management vlan, and the wireless vlans to it, about 14 vlans in all. 

I've configured airplay and chromecast services to be shared and under Monitor->BonJour Gateway it's all working correctly as shown 

When I try to access these services using an Android device it can only see the chromecast service when I try casting only about 20% of the time, I tried installing a Bonjour Browser app and the service list seems to disappear then appear again.

I can't really think of what else to look at now, it appears to all be working correctly (some of the time), the service list isn't particularly long and the list of services being shared is tiny. I've got a similar setup with Reflector and android working on a Cisco Wireless Controller on a different site without issue and when we were using it during testing on 1 vlan it all worked correctly too.

Is there anything I've missed or that I can look at?
Photo of David Sullivan

David Sullivan

  • 4 Posts
  • 1 Reply Like

Posted 3 years ago

  • 1
Photo of Nick Lowe

Nick Lowe, Official Rep

  • 2491 Posts
  • 451 Reply Likes
The Bonjour gateway is stateless these days and relays from one broadcast domain to others.

Have you tried looking at a packet capture with Wireshark to see what's going on?
Compare and contrast what's happening in the source broadcast domain to a target broadcast domain.

You should find that the MDNS in the source broadcast domain is relayed straight away to the others, as per the configuration.

I'd be minded to check that it's not packet loss of the multicast UDP that is causing your issue.

Does it function as expected when you're in the same broadcast domain?
Photo of Crowdie

Crowdie, Champ

  • 972 Posts
  • 272 Reply Likes
Off the top of my head:
  • Are your traffic filters blocking inter-station traffic?
  • Have you enabled multicast to unicast conversion?
Photo of Matthew Gast

Matthew Gast

  • 284 Posts
  • 63 Reply Likes
Nick's questions are good ones.  Regardless of which BGW version (stateful or stateless) you have, you should be able to see mDNS queries and responses.  When the service disappears, I'm interested to know whether it is because there's no mDNS replies, or because you actually get a service withdrawl message.