Hi Community,
maybe you are wondering what I plan to do, just because of the title, but nevertheless you opened this threat. :-)
So, I've got a small remote office with some users, they have a small utm, DSL Line, no static IP, typical small environment. But they have their own User directory and their own Fileserver, where they want to have access to. It would be easy to give them SSL-VPN Remote Access, but they don't have a static IP. I don't want to mess around with dyndns.
And I have my main office, where I have a public IP-Network and a big UTM and so on.
So in order to give them the chance to do Remote Access I thought it could work out to establish a IP-SEC Tunnel from the small-office to the main office and to give them a small public ip-network over the ip-sec connection. So far, so good, but how to bind the SSL-VPN to the tunnel. Since you can only select "real network interfaces" on the ssl settings tab, I don't see any chance to bind the ssl-vpn to the "tunneld" pubilc IP address.
Got my problem? Anyone been so crazy as to try something like this bevore?
Regards, Rolf
This thread was automatically locked due to age.