Fortigate routing issues over IPsec VPN
Posted on 2014-10-14
We have a Fortigate 310B, which is our firewall.
We have multiple IPsec VPN tunnels to different companies and from several branch offices etc.
After creating a new physical interface we are seeing that remote locations(branch offices etc.) which is connected to us attempts to use the new physical interface as the default gateway when routing over the IPsec VPN tunnel.
Created another new physical interface, and the issue is the same. The only difference is that remote users over IPsec now sees this interface as their gatway, when routing over the IPsec Tunnel.
Applies only to interface/Route based IPsec VPN tunnels.
The routing sill works from remote locations over IPsec VPN, however we have a a few VPN Concentrators which is critical to our branch offices to access other companies network. As long as a new physical interface is active with an IP-Address the concentrator stops working all together.
Examples where a user from remote location 192.168.133.0/24 tries access a server at our Lan 172.22.0.0/20 and a remote company over a concentrator.
Without the new physical interfaces, the routing is normal
With a new physcial interface
With new physical inteface and to remote company over ipsec
* * * timeout
* * * timeout
Our physical interfaces are as follow:
P1 Internet: Public IP
P5 LAN: 172.22.0.0/20
P9: 172.22.29.1/24 (newly created)
Anyone experienced anything similar with a Fortigate or know what is causing this issue ?