AltostratusResolving internal IP's externally using SNAT or HTTP profile or another method?
The simplest way for me to explain what I have been trying to accomplish is with pictures.
We host a website on our Internal 192.168.x.x network, the client connects through a Portal Access Link to the webserver and downloads a Java webstart file. The client will enter the IP address of an internal 192.168.x.x terminal server and the connects gets resolved by the F5 to allow the user to connect from an External network to an internal network address. The problem is the applet is not hosted by the F5, so the connection no longer persists on the F5. Yes we can host this applet from the F5 and the connects work, however this is not what we want to accomplish.
First my question is if this is even possible.
I have tried making a virtual server with this internal ip (192.168.x.x) on my external Vlan. I was actually able to ping the address and do a tracert to the IP. However the next day I was unable to ping this address again, and I don't think I changed anything. When the ping worked, after analyzing the traffic, it indeed went to the F5, but it did not traverse through the F5 to the other side.
My theory is, by having a virtual server with the internal ip on the external vlan, Then rewrite the headers or do SNAT so the connection will go through the F5 and reach the internal network.
Am I barking up the wrong tree with this? Is there a better solution to try to accomplish this?
It would be nice to simply do something like this, picture taken from SNAT section in the F5 Manual:
