Because of the highly custom nature of a VPN, we are not able to support this type of use. However, we are happy to provide some guidance to assist in the setup process if this is your goal.
If you set up a VPN correctly then any remote devices will obtain an IP address within the subnet of your home/office network. As long as the following ports are open, your iOS device won't be able to tell the difference and you should be able to use your airplay connection over VPN:
Port | Type | Protocol | RFC | Used By |
80 | TCP | HTTP | 2616 | AirPlay |
443 | TCP | HTTPS | - | AirPlay |
554 | UPD/TCP | RSTP | 2326 | AirPlay |
3689 | TCP | DAAP | - | iTunes Music Sharing/AirPlay |
5297 | TCP | - | - | Bonjour |
5289 | TCP/UDP | - | - | Bonjour |
5353 | UDP | MDNS | - | Bonjour/AirPlay |
49159 | UDP | MDNS (Windows) | - | Bonjour/AirPlay |
49163 | UDP | MDNS (Windows) | - | Bonjour/AirPlay |
There are a few common scenarios that we might see when dealing with using Airplay over a VPN.
- The AirPlay sender and receiver are in the same network, but the sending device is connected to a VPN. In this case, the AirPlay sender may not see Reflector (or an Apple TV). When this happens, the VPN provider should consider offering a "split VPN" that selectively routes traffic over the VPN depending on the destination. If the AirPlay sender is an iOS device there are limited options for this, but computers running AirParrot can manually add the route, overriding the VPN.
- The computer with Reflector is connected to VPN, AirPlay sender is not on the VPN. This is essentially the same scenario as above in reverse, and can likely be solved with a split VPN or static route.
- Reflector and Airplay sender are on different networks with a VPN between them. In this case, the VPN server would need to be configured to support Multicast traffic while using a single subnet. For this type of use, your IT team should research this with your VPN vendor.