
Not applicable
Created on ‎09-30-2011 01:46 AM
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Problem Communication between two interface on Fortigate
Hello Everyone.
To begin excuse me for my english i' m french
So my problem concern a communication between different interface.
My network is that :[image][/image]
I want my computer in the LAN1 could communicate with the LAN2 cross the WAN2 interface , the network between the two lan is OK, i can ping all object since my fortigate. I configure a route map for the LAN2 cross the Router Virtual IP.
The gateway of my computer in LAN1 is the internal interface. But the fortigate routing the communication between INTERNAL and WAN2 interfaces no ?
So i would all computers in LAN1 can communicate with the WAN2 to communicate with the LAN2.
I don' t know if i have been clear and excuse me again for my english.


1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
and welcome to the forums!
Avant tout, pas de problème avec votre English. We' ve had discussions in Spanish and some other languages here. And it' s clearly understood what you want to achieve.
To let traffic flow between LAN2 and LAN1 you need:
- a static route on the FGT specifying that LAN2 subnet is behind 192.168.2.3
(the route to LAN1 is already there as LAN1 is directly connected)
- a policy from ' internal' to ' WAN2' , allowing ALL services, no NAT
- a policy from ' WAN2' to ' internal' , allowing ALL services, no NAT
and on LAN2:
- clients must have either a static route to the LAN1 subnet or a default route via the external VRRP virtual IP (which is missing in your otherwise excellent image)
on LAN1:
- same but for LAN2, and gateway is the FGT
Now for testing:
- how far can you ping from a host on LAN1? use traceroute if you' re lazy
- how far can you ping from a host on LAN2? use traceroute if you' re lazy
Do not ping from the FGT' s console at the moment as it might be a missing route on the hosts.
Ede Kernel panic: Aiee, killing interrupt handler!
Ede Kernel panic: Aiee, killing interrupt handler!
