i3ALLSYNC Sender Client device – Technical Requirements:
Laptop and mobile device
Laptop and Tablet PC
iPads and iPhones
Android Tablets and Phones
Windows 10 or newer.
Mac OS 10.15 or newer.
iOS version 7.0 or newer.
Android 5.0 or newer.
Intel Core 2 Duo, 2.3GHz, or AMD equivalent, 2 GB RAM.
iPad 3 / iPhone 5 or newer.
Phones/Tablets with Android 5.0 or newer.
Intel Core i5 with 2C4T, 2.3GHz, or AMD equivalent, 6 GB RAM.
iPad 3 / iPhone 5 or newer.
Phone/Tablets supporting Android 5.0 or newer.
i3ALLSYNC Windows Receiver server – Technical Requirements:
Host Computer for i3ALLSYNC Windows Rx
Windows 10 or newer.
i3ALLSYNC Windows Software is not supported in a virtual machine (VM) environment or while using terminal services.
Intel Core i5 with 2C4T 2.3GHz or higher, or AMD equivalent.
Direct X 11 or higher, Integrated Intel HD Graphics or Dedicated Graphics (AMD Radeon or NVIDIA GeForce.)
Single NIC Card. Ethernet Connection.
When i3ALLSYNC is deployed into the existing network, the host PC and the clients require a wired or wireless network connection with a minimum bandwidth of 20 Mbps. When running HD content, increase the minimum bandwidth to 50 Mbps. Like any network application, the overall performance would be depended on available bandwidth. Internet access is required to activate the i3ALLSYNC receiver server and install software updates. Internet access is also required to install and update the i3ALLSYNC client apps for Windows, Mac, and Android.
In addition to allowing the software to communicate through any security barriers in place (such as antivirus or firewalls), the network must also be capable of using the correct communication protocols required for the automatic discovery of your mirroring device. Included below is an overview of all networking requirements needed to use Bonjour services such as AirPlay properly.
Local traffic only:
AirPlay applications use a direct connection method through the local network. The i3ALLSYNC receiver is directly connected to Apple devices.
You must be on the same VLAN or subnet within the network to connect; Apple's AirPlay cannot cross subnets/VLANs natively, this is a limitation of Apple's AirPlay. If you require the connecting devices to be on different subnets, then you may wish to have the IT department look into a Bonjour Gateway for the network. Some network hardware will have this functionality built-in and others may require a third-party solution.
The Bonjour Gateway and airplay proxy will allow AirPlay to cross subnets/VLANs so your devices may communicate. This, however, will show all AirPlay devices on the network, so the users may wish to change the broadcast name and add an AirPlay password as well.
The local network must be allowed to run Bonjour, mDNS, and Multicast must be enabled. The Bonjour protocol consists of service announcements and service queries that allow devices to ask for and advertise specific applications, such as AirPlay. For our purposes, we are primarily concerned with AirPlay availability.
Each query or advertisement is sent to the Bonjour multicast address for delivery to all clients on the subnet. Apple’s Bonjour protocol relies on Multicast DNS (mDNS) operating at UDP port 5353 and sends to these reserved group addresses:
- IPv4 Group Address - 184.108.40.206
The addresses used by the Bonjour protocol are link-local multicast addresses and thus are only forwarded locally. Routers cannot use multicast routing to redirect the traffic because the time to live (TTL) is set to one, and link-local multicast is meant to stay local by design.
AirPlay ports must be available on the subnet or VLAN being used to connect your devices as well. Here is the port list that AirPlay will use with our applications:
- IPv4 Group Address 220.127.116.11 port 5353 (MDNS - Apple) (These ports are used for AirPlay detection on the network)
- TCP port 7000 (airplay protocol), other dynamic TCP ports (for mirror), and UDP port (for RTP audio.)
- The receiver will also access TCP 80/443 for any directly connected videos (such as YouTube), and that should be the only external access the application uses. Everything else will be local traffic with no need to access the internet.
Some networks may use a Multicast group to manage multicast traffic. When multicast is enabled, then all multicast traffic will flow to all connected clients in a subnet. Using a multicast group to limit the number of clients receiving the multicast data reduces the overall workload being placed on the network.
Using groups is typically not required, but it can help many AirPlay devices on the network. When creating multicast groups, there are 3 important factors to consider:
- Multicast groups must include the subnets or VLANs where AirPlay devices (and clients that may mirror those devices) are connected.
- All AirPlay devices and clients must be members of the multicast group.
- If using multicast groups, then IGMP Snooping must be enabled on your network to allow your devices to listen to the multicast group. This allows your devices to see the multicast group traffic without affecting the rest of your network.
Using all of the above information contained in this guide, you should ensure that any network is compatible with i3ALLSYNC AirPlay and the Bonjour services.