Skip to main content
fferraro87
New Member
September 4, 2018
Question

routing between two different subnet on two different port

  • September 4, 2018
  • 4 replies
  • 7633 views

Hi,

like you can see from image attached i've two different servers connected to my fortigate 100D on two different internal port. So i've 192.168.3.0/24 on port 3 and on port 4 i've defined many VLAN and there is a VLAN called VLAN 70 that has 172.16.70.0/24 subnet. Now i've to communicate using their private ip, it's possible? i've try to add a policy like that :

 

config firewall policy
    edit 114
        set name "lan port3 to VLAN 70"
        set uuid 6a55395a-b017-51e8-f2b8-e066fb5ec046
        set srcintf "port3"
        set dstintf "VLAN70"
        set srcaddr "192.168.3.190/32"
        set dstaddr "172.16.70.100/32"
        set action accept
        set schedule "always"
        set service "ALL_ICMP"
    next
end
But that policy isn't matched. I've try also to debug connection but i've no trace. It's possible to do that? Thanks

4 replies

tanr
New Member
September 4, 2018

I think that looks right.  You're just trying to ping the host on VLAN70 from the host on port3 and it fails?

 

Is it possible you're hitting another security policy before this one and the ping is getting handled/blocked by that?

What do the logs say for which policy handled this ping?

fferraro87
New Member
September 4, 2018

tanr wrote:

I think that looks right.  You're just trying to ping the host on VLAN70 from the host on port3 and it fails?

 

Is it possible you're hitting another security policy before this one and the ping is getting handled/blocked by that?

What do the logs say for which policy handled this ping?

i don't see anything from debug flow, that's strange.

for debug i do these command on console :

 

diag debug reset
diag debug enable
diag debug console timestamp enable
diag debug flow show console enable
diag debug flow filter saddr 192.168.3.190
diag debug flow filter daddr 172.16.70.100
diag debug flow trace start 100

 

but i don't see anything when i ping from 192.168.3.190 to  172.16.70.100

 

tanr
New Member
September 4, 2018

If you enable ping on port3 lan interface itself, can you ping the interface from the host?

Thought Leadership Security Summit. Outpace New Threats with AI - enhanced defense. Tuesday, Septmeber 15, 8:30 AM - 2:30 PM PT. The Golf Club at Newcastle, WA.
Virtual event | September 2026. SASE summit. The age of autonomous trust. Register here!