The clients in both subnets automatically use one of the Caching servers in their organization’s network (in the figure, one subnet has two servers to illustrate that you don’t need a Caching service for each subnet behind NAT). The clients and the Caching servers in both subnets have the same public IPv4 source address on the public Internet side of the NAT device, even though they are in different subnets. In the following figure, a network device performs NAT, and the organization has two subnets. Otherwise, the client will use servers operated by Apple or a content distribution network partner (just like they did before the Caching service was introduced as a feature). (This applies even if the client and the Caching server are on different subnets, as long as they have the same public IPv4 source address.) Fortunately, this is a common configuration.Įligible clients will automatically use the appropriate Caching server.
The key is that your clients and the Caching server(s) must share the same Internet connection behind a NAT device, and their traffic from your network to the Internet must have the same source IPv4 address.
Reference 16.1 Understanding the Caching Serviceįor eligible computers and devices, the Caching service transparently caches many items, including: Apple gave this service a new name: Caching Server 2. More Info ▶ One big new feature in the Caching service for OS X Server for Mavericks is that it serves iOS 7 devices. This allows you to save time as well as Internet use. This means you can offer fast downloads of items distributed by Apple to clients on your network. It caches the first download of various items distributed by Apple, then makes these items available to devices and computers on your local network. The Caching service speeds up the download and distribution of software and other content distributed by Apple.
0 kommentar(er)
