Allow traffic from ssl-vpn to enter ipsec tunnel

[evince]

Hello all,

I'll try to explain my scenario.

My office (192.168.7.0/24) has an ipsec to a remote location (10.133.3.0/24). My office subnet is natted to 172.31.19.0/24.

So IPSec (tunnel mode, not interface) is set between 172.31.19.0/24 to 10.133.3.0/24.

I'd like to use SSL to connect to my office (it's working), but i'd like to reach remote subnet (10.133.3.0/24).

How to do this?

Thank you in advance,

Kind Regards,

[ede_pfau]

1- routing

2- policy

[evince]

Hello ede_pfau, and thank you for your support. Can you explain me a little bit more how to achieve this please?

Thank you in advance,

[ede_pfau]

(I knew it. Sorry.)

What I wanted to say is that the setup is doable and relatively simple.

First, routing. The client has to have a route to the second network, or traffic will not go across the SSLVPN to reach the FGT.

On the FGT, you will need a route to the network behind the SSLVPN (i.e. your clients) pointing to the 'ssl.root' interface, and a route to the network behind the IPsec tunnel. Imagine visiting each hop on the way from the client to the IPsec network and back: client - FGT - tunnel - IPsec network. At each hop a route to the next hop and back to the previous hop is needed. Sometimes a static explicit route, sometime a default route (to make life easier).

Second, if all participants know how and where to send the traffic, then you additionally need a policy to allow it. After all, the FGT is a firewall, a control device. For writing the policy, you need address objects of the source and destination networks, the services you allow, some UTM...

In short, both the SSLVPN and the IPsec VPN are represented as virtual ports on the FGT. You route and allow traffic between these ports just like between any pair of physical ports.

[evince]

Thank you for your fast reply.

Here is what i have configure :

- Static route Dest 10.133.3.0/24 Device ssl.root

- Policy Src=ssl.root Dest=10.133.3.0/24 Action=Accept

I'm running 5.2.4, and i do not have any policy with SSL as Action as it is not showing anymore (removed sinve ver5.2 i mean)

I'm trying a traceroute and it is blocking first hop (the ip of my SSL connection)

The SSL pool is 192.168.7.222-192.168.7.225

Kind Regards,

[rwpatterson]

evince wrote:
- Static route Dest 10.133.3.0/24 Device ssl.root

The SSL pool is 192.168.7.222-192.168.7.225

The static route should point to the IP addresses in the SSL IP pool.

[ede_pfau]

...right, and there should be a static route to 10.133.3.0/24 pointing to the IPsec tunnel interface.

Please post the entire policy - interfaces, addresses.

[evince]

Hello and many thanks :)

As it is a tunnel mode IPSec and not an Interface mode, i can not point to the IPSec tunnel interface.

   edit 155         set srcintf "Lens"         set dstintf "wan1"         set srcaddr "Lens_Subnet" (192.168.7.0/24)         set dstaddr "Cloud_Systemat" (10.133.3.0/24)         set action ipsec         set schedule "always"         set service "ALL"         set natip 172.31.19.0 255.255.255.0         set comments "natted to 172.31.19.0/24"         set inbound enable         set outbound enable         set natoutbound enable         set vpntunnel "Lens_To_Cloud"     next

[ede_pfau]

This mode is called "policy-based" vs. "interface-based" IPsec VPN. Both generate tunnels.

Best to re-create the VPN in interface mode. There is no direct way to reconfigure it. I don't see any other way to get the routing done.

[rwpatterson]

ede_pfau wrote:

This mode is called "policy-based" vs. "interface-based" IPsec VPN. Both generate tunnels.

Best to re-create the VPN in interface mode. There is no direct way to reconfigure it. I don't see any other way to get the routing done.

Yes, you have to break it down and rebuild it. Sorry, no magic wand here.