routing - vpn

[nikotron]

I' ve 3 fortigate a -b -c a is connected to b wirh ipsec vpn a is connected to to c with ipsec vpn lan a is 192.168.1.0 lan b is 192.168.4.0 lan c is 192.168.5.0 i' d like to connect b and c using a as gateway? anyone may help me with config? Thank you in advance Nicola Ginanni

[Mark_Oakton]

Hi Nicola, What are you trying to achieve, full mesh vpn with redundant routes? Let us know what you are trying to do Mark

[Jan_Scholten]

Have a dynamic routing protocol or static routes in place (e.g. have a route for network of b visible/configured at c). So the remote sites " know" that the other site is reachable via a. Have a policy (i assume Tunnel/interface based VPN) from Tunnel to A -> Tunnel to C and vice versa. should be pretty easy to setup.

[nikotron]

Deal all very thank you for your support i try to explain better my situation fortigate 140d on lan 192.168.1.0 fortigate 40c on lan 192.168.4.0 fortigate 40c on lan 192.168.5.0 both 40c are connected to 140 d with interface based vpn and eveything is working fine. subnet 192.168.4.0 and 192.168.5.0 can ping and comunicate with 192.168.1.0. i' d like to connect 192.168.4.0 with 192.168.5.0 using 192.168.1.0 or 140 d as gateway i added this static route on 40 c 192.168.4.0 : 192.168.5.0/2555.255.255.0 and as gateway the vpn interface i used for 192.168.1.0 vpn is correct? whsn i make tracert from 192.168.4.0 to 192.168.5.99 they stop 192.168.4.99 that is my fortigate 40c what is wrong? can you make me same example of working config? Thank you in advance Nicola