SWGFL to block Apple Caching Server

[mwnci]

28/05/14 - iOS7 update incident call 4521375

There is currently a known interoperability issue with Apple's OS X Caching Service and large wide area networks implementing proxy services (including RM's SafetyNet Plus service). Due to the way in which Apple has implemented the default configuration for the Caching Service, RM customers who run the OS X Caching Service can prevent other RM customers downloading updates and apps for Apple devices running iOS7 and above.

 

In order to ensure all customers retain the ability to download updates and apps for their Apple devices, RM is restricting access to the Apple Caching Service registration system. The restriction will be implemented on the evening of Tuesday 3rd June 2014. We apologise for the inconvenience this may cause some customers.

[mwnci]

I'm waiting to hear if there is a work around - but this is a real shame as the Apple Caching Server has solved a lot of problems for us.

[snagrat]

Just another reason to move away from SWGfL.....

[Abe]

I think I've managed to get the Apple Caching Service working for a SWGfL connected school, although this may not be an option for many unless like us you happen to have a backup ADSL Internet Service.

 

I found this blog useful to start me in the right direction: Fraser Hess: Caching Server: Enterprise Edition

 

SWGfL appear to block connection to the Apple site needed to register a caching server, so it was necessary to provide an alternative path (via our ADSL connection). Once successfully registered as a caching server and with the required DNS entry added to our local DNS servers, I was able to see the "Cache Used" start to show content building up as I downloaded updates on a Mac client.

 

I used a SWGfL public address range of 46.60.253.1 - 46.60.253.254 and also had to specify a public address range that included the public IP of the caching server Mac going via our backup ADSL connection.

 

This has the potential to save a lot of Internet bandwidth for us in future.

[localzuk]

I think I've managed to get the Apple Caching Service working for a SWGfL connected school, although this may not be an option for many unless like us you happen to have a backup ADSL Internet Service.

 

I found this blog useful to start me in the right direction: Fraser Hess: Caching Server: Enterprise Edition

 

SWGfL appear to block connection to the Apple site needed to register a caching server, so it was necessary to provide an alternative path (via our ADSL connection). Once successfully registered as a caching server and with the required DNS entry added to our local DNS servers, I was able to see the "Cache Used" start to show content building up as I downloaded updates on a Mac client.

 

I used a SWGfL public address range of 46.60.253.1 - 46.60.253.254 and also had to specify a public address range that included the public IP of the caching server Mac going via our backup ADSL connection.

 

This has the potential to save a lot of Internet bandwidth for us in future.

 

You might also be making problems for the rest of us though by doing that, if you look at the original notice.

[Abe]

You might also be making problems for the rest of us though by doing that, if you look at the original notice.

 

I have selected the Cache content for clients connecting from: "only local subnets" option, so it should be OK, but then again my experience with Macs to date is that a lot of things that should work don't tend to!

 

In any case, no clients from other schools will be able to see the DNS entry on our local servers that specifies the Apple Cache public IP range to use.

[snagrat]

Is this still being block by SWGfL then?

[lwrona]

Do you know if this is still the case, please?

[Daryn]

Finally light at the end of the tunnel!

 

https://esi.swgfl.org.uk/support/technicalarticle.asp?cref=tec5063184