Solved

Fortigate routing issues over IPsec VPN

Posted on 2014-10-14
8
956 Views
Last Modified: 2014-11-23
Hi

We have a Fortigate 310B, which is our firewall.
Firmware: 5.0.7

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
Tracert 172.22.1.11
192.168.133.1
172.22.0.1
172.22.1.11

With a new physcial interface
Tracert 172.22.1.11
192.168.133.1
172.22.29.1
172.22.1.11

With new physical inteface and to remote company over ipsec
Tracert 10.60.60.100
192.168.133.1
172.22.29.1
* * * 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 ?

Regards.
0
Comment
Question by:Lenblock
  • 5
  • 2
8 Comments
 
LVL 38

Expert Comment

by:Aaron Tomosky
ID: 40381342
No personal experience, but my google-fu has found references to the placement of the policy in the config having effects like this.
http://community.spiceworks.com/topic/409597-fortigate-80c-configuring-an-interface-mode-ipsec-site-to-site-vpn
0
 

Author Comment

by:Lenblock
ID: 40381814
Hi

Tried that, without luck.

I've set the physical interface to deny ping (icmp), and created no policies for it.
The remote computer still uses the Physical interface as a gateway.
0
 
LVL 38

Expert Comment

by:Aaron Tomosky
ID: 40382579
Perhaps this will help?
http://www.experts-exchange.com/Hardware/Networking_Hardware/Firewalls/Q_25099833.html

Hopefully someone with more fortigate experience will show up.
0
 
LVL 20

Expert Comment

by:Jakob Digranes
ID: 40383726
what routes are setup for the device?
0
Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.

 

Author Comment

by:Lenblock
ID: 40383934
Hi

Static routes for the following:

Default route to internet.
All IPsec VPN Interface Based Tunnels.
All Branch offices which is connected over our IPS's network

Regards.
0
 

Author Comment

by:Lenblock
ID: 40386270
Hi

Possibly found the cause for this.

Each Interface on the Fortigate is given an index number.
When creating the new interface on port9 it was given an index number lower than port5.
Fortigate decides which interface should be used as the next hop based on the index number.

Therefore remote computers over an IPsec Interface would use port9 as their next hop.

Looking into how we would go about changing the index number for an interface.
Not yet found out how.

Anyone know how or can suggest a different solution ?

Regards.
0
 

Accepted Solution

by:
Lenblock earned 0 total points
ID: 40451735
Hi

For any others looking for the answer:
If you enable multiple networks on multiple ports on a fortigate without vdom it will use the port with the lowest index as the default next hop in routing. You cannot change the index number. This is a problem if you have a IPsec concentrator.

Enabling vdom and separating the additional network solves this issue.
0
 

Author Closing Comment

by:Lenblock
ID: 40460415
Enabling vdom solves it.
0

Featured Post

Enabling OSINT in Activity Based Intelligence

Activity based intelligence (ABI) requires access to all available sources of data. Recorded Future allows analysts to observe structured data on the open, deep, and dark web.

Join & Write a Comment

Suggested Solutions

What’s a web proxy server? A proxy server is a server that goes between clients and web servers, used in corporate to enforce corporate browsing policy and ensure security. Proxy servers are commonly used in three modes. A)    Forward proxy …
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
Get a first impression of how PRTG looks and learn how it works.   This video is a short introduction to PRTG, as an initial overview or as a quick start for new PRTG users.
Here's a very brief overview of the methods PRTG Network Monitor (https://www.paessler.com/prtg) offers for monitoring bandwidth, to help you decide which methods you´d like to investigate in more detail.  The methods are covered in more detail in o…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

13 Experts available now in Live!

Get 1:1 Help Now