Jump to content

Apple Caching Server for LAN + VLAN


Recommended Posts

Posted

Hey all,

 

I'm attempting to setup an Apple Caching Server before Apple releases iOS 8 on Wednesday 17th 2014.

I've installed Server, enabled the Caching Server, set a limit and it all seems to be working.

 

BUT.

 

I have 2 networks.

 

Regular LAN (192.168.x.x) for all the PCs, labs, laptops etc...

VLAN (10.0.x.x) for mobile devices.

 

The caching server is currently connected to the regular LAN (192.168.x.x) but I would like it to cache content for the VLAN (10.0.x.x) as well.

Both LAN & VLAN go through the same smoothwall firewall and share a common public IP that part is sorted.

 

What's the best way to get this working?

 

Thanks!

Posted
on your mac server you need to add the vlans as a network then in the config of the caching server add the interfaces - thats what ive done on mine and its working a treat
  • 3 weeks later...
Posted

@bshingler - Thanks, how do I add the interfaces to the caching server? As far as I can see there aren't any config options?

 

At the moment I have it configured:

 

Eth0 -

IP: 192.168.0.65/255.255.224.0

GW: 192.168.0.25

DNS: 192.168.0.1

 

Eth0 (VLAN 5) -

IP: 10.0.0.3/255.255.224.0

No gateway or DNS (I don't think it needs 2 routes to the internet?)

 

And on the caching server I have "only cache content for local networks" checked.

 

Is this correct?

Posted (edited)

I see this in the debug.log file:

 

2014/10/03 09:25:41:065 Registering with local address: 192.168.0.65

2014/10/03 09:25:43:466 Request for registration from https://lcdn-registration.apple.com/lcdn/register succeeded

2014/10/03 09:25:43:466 Got back public IP 196.30.xxx.xxx

2014/10/03 09:25:43:469 This server has 0 peer(s)

 

Which means it's correctly registering with the 192.168.0.65 address, but what happens if a user on the 10.x.x.x VLAN requests an update from Apple?

Device: "Hi Apple, I'd like this update, my public IP is 196.30.x.x"

Apple: "Sure, there's already a caching server on your network, its address is 192.168.0.65"

Device: "But my address is 10.x.x.x, i can't access 192.168.0.65"

Apple: "I SAID, THE ADDRESS IS 192.168.0.65. DEAL WITH IT."

Edited by Nick_Parker
  • 3 months later...
Posted

Hey all, quick update:

 

I've got the caching server setup with the following settings:

 

Eth0 -

IP: 192.168.0.65/255.255.224.0

GW: 192.168.0.25

DNS: 192.168.0.1

 

Eth0 (VLAN 5) -

IP: 10.0.0.3/255.255.224.0

No GW or DNS

 

And within the Caching Server I've got it set to cache to "All Networks".

 

Quite a few staff & students have come to me and said that their apps won't update.

As soon as I shutdown the Caching Server, their apps update.

 

What have I done wrong?

Posted

I've just had a look in the debug.log for the caching server and here is the output:

2015-02-03 07:56:33.763 Caching Server started

2015-02-03 07:56:33.934 Server GUID is 8AF19D1C-80D4-467C-85BB-B25F6189E74A

2015-02-03 07:56:35.316 Cache manager initialized, cache limit = unlimited, current cache size = 14.12 GB

2015-02-03 07:56:35.316 xpcListener should be running

2015-02-03 07:56:35.317 HTTPServer: Started HTTP server on port 50689

2015-02-03 07:56:35.317 Retrieving configuration

2015-02-03 07:56:35.599 Request for configuration from http://suconfig.apple.com/resource/registration/v1/config.plist succeeded

2015-02-03 07:56:36.403 Cleaning cache

2015-02-03 07:56:36.611 Cleanup succeeded.

2015-02-03 07:56:36.611 Registering for notifications

2015-02-03 07:56:36.622 Registering for service

2015-02-03 07:56:40.575 Registering with local address: 192.168.0.65

2015-02-03 07:56:41.349 Request for registration from https://lcdn-registration.apple.com/lcdn/register succeeded

2015-02-03 07:56:41.349 Got back public IP 196.30.x.xxx

2015-02-03 07:56:41.420 Registration succeeded. Resuming server.

2015-02-03 07:56:41.421 This server has 0 peers

 

It looks like it's completely ignoring the 10.0.0.0/19 network even tho it's set to cache for all networks?

Posted
The 192.168.0.0 and the 10.0.0.0 range need to be routable from each other. Because the server only advertises one internal Ip via Apple. E.g. The client on 10.0.0.0 range will get a message from Apple that their is a local cashing server at 192.168.0.X and the 10.0.0.0 needs to be able to get to it through your router.
Posted

Thanks @MicrodigitUK

 

I'm busy testing a similar solution, I removed the 192.168.0.0 NIC and left the 10.0.0.0 NIC, In smoothwall I then created a Zone Bridge allowing all traffic on the 192.168.0.0 Network bi-directional access to 10.0.0.2 on the 10.0.0.0 network and it *seems* to be working at the moment. Will continue testing and let you know :)

  • 1 year later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...