CacheGuard Help

Hi David, The CacheGuard is not cabled in yet. Our expectation is that on the inside of the network, we would have a private address in the 10.2.0.0/23 network and on the outside - pointing to the router, we would have a public ip address. We need a recommendation as to which one we call "inter...

Hi David, We are getting closer but no cigar yet. I can get the unauthenticated users to use the proxy by explicitly using an ip address in the URL rather than a domain name - in fact, because of the L3 firewall at this stage, it is mandatory. I would then need the proxy to map to a specific URL or ...

The need is to be able to reach the content delivery servers using a fixed ip address in the URL rather than a domain name. This will allow the firewall to be set up properly. The proxy should take the URL of the form "https://10.2.0.x/page&parameter list" from the WLAN controller and ...

Thanks for your response. I have not reviewed the documentation links yet but based on your description of a possible solution, I do not think it will work as planned. The public servers are already cloaked and their ip addresses are not known nor can they be known - this is creating the problem. Wh...

Yes, your understanding is correct.

Prior to authentication on a Wi-Fi network, users are presented with content that can come from multiple ip addresses on the web. The firewall in the Wi-Fi controller that is used prior to authentication will not accept domain names – only ip addresses. The nature of the content supplier(s) networks...