Thanks
@cjoseph @cjoseph.
The settings before I changed anything is Broadcast Filtering - ARP.
The clients and the mDNS sharing device are in the same VLAN. The devices supports two networks, one wired, and the other wireless. We want wired for the Private network and wireless for Guest.
The wireless clients on the Private network can see the sharing device, but cannot consistently connect. Sometimes they connect, sometimes they do not. Sometimes after connecting, they disconnect.
The wireless clients on the Guest network cannot see the sharing device, unless I disable Broadcast Filter. The experience then, is the same as the users above on the Private network, inconsistent.
From what you stated, it sounds like AirGroup is not needed. However, I do want the best performance, so if AirGroup would help, please advise.
------------------------------
Christopher
------------------------------
Original Message:
Sent: May 11, 2022 12:50 PM
From: Colin Joseph
Subject: mDNS, WiFi display sharing device failures on Aruba AP's
If you just have an "allow all" firewall policy for your roles, all your clients (and the screenbeam devices) are in the same VLAN and broadcast filtering is disabled, your clients should be able to see your screenbeam devices without enabling Airgroup.
You would need Airgroup if:
- Your clients and screenbeams are not in the same VLAN, and you need them to see each other
or
- You want to improve performance by enabling broadcast filtering and you still want your clients to see your screenbeam devices.
Try to put everything in the same VLAN and disable broadcast filtering first to ensure that you don't have a separate issue.
------------------------------
Any opinions expressed here are solely my own and not necessarily that of Hewlett Packard Enterprise or Aruba Networks.
HPE Design and Deploy Guides: https://community.arubanetworks.com/support/migrated-knowledge-base?attachments=&communitykey=dcc83c62-1a3a-4dd8-94dc-92968ea6fff1&pageindex=0&pagesize=12&search=&sort=most_recent&viewtype=card
Original Message:
Sent: May 09, 2022 10:53 PM
From: Christopher Baulckim
Subject: mDNS, WiFi display sharing device failures on Aruba AP's
I am looking for guidance on WiFi display sharing devices, such as that of the Screenbeam 1100 here, https://www.screenbeam.com/products/screenbeam-1100-plus. We purchased one for our organization. I configured and tested it at home in a Cisco LAN environment with Meraki AP's, and it worked flawlessly. I took it into the building expecting the same, which has the same Cisco LAN, but Aruba AP's, Wi-Fiand it worked one time on the Internal network, and never on the guest network. It then stopped worked completely. I took it back home, and again it works great.
On the Aruba Instant AP network, I tried the following:
- Turned on AirGroup with Enable Bonjour, Guest Bonjour multicast, allowall, but it still didn't work
- On the guest network, I set Broadcast filtering to Disabled, and Deny inter user bridging to off, but it still didn't work
We are using Aruba AP 535's on 8.8.0.2. The user clients and Screenbeam devices are in the same vlan.
Any ideas?
The network requirements from the manufacturer are:
Multicast DNS (mDNS) support is required for iOS and macOS native screen mirroring
to auto-discover ScreenBeam
Required ports
• 5353 (UDP) for Multicast DNS (mDNS) discovery
• 7100 (TCP and UDP) for macOS, iOS and Windows 10 mirroring
• 7250 (TCP) for Miracast over LAN data stream
• 47000 (TCP) for Airtunes in AirPlay
• 18000-18009 (TCP) for macOS and iOS AV data
------------------------------
Christopher
------------------------------