Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Hello @AliAllafzadeh ,
You need to configure 2 routes.
First, configure the route on the route table like this,
Address Prefix: 0.0.0.0/0.0.0.0
Next hop type: Virtual Appliance
Next hop IP: 172.16.136.68
Second, configure the route on Fortigate like this,
Destination : 192.168.0.0/24
Gateway: 172.16.136.65
Device: Port2
Example for azure side
Hello @AliAllafzadeh ,
No need to vnet peering for this case. Did you configure a static route for the new subnet on FortiGate?
Also, can you check the traffic flow on Fortigate with this command? With this command, we can ensure whether traffic reaches Fortigate or not.
diagnose sniffer packet any 'host 192.168.0.x' 4 a ( "x" should be changed with client IP)
After running this command can you try to reach somewhere?
Created on 04-03-2024 04:21 AM Edited on 04-23-2024 12:28 AM
Delete it please
Created on 04-03-2024 04:28 AM Edited on 04-03-2024 04:43 AM
Hello @AliAllafzadeh ,
No need to configure the interface for each new network.
But you should configure the gateway IP address with your ILB IP address. When I look at the screenshot you sent. You need to change the gateway IP address to 10.2.8.65.
And you say we added a new network with 192.168.0.0/24 prefix. You need to configure a static route like this.
Destination : 192.168.0.0/24
Gateway: 10.2.8.65 or your ILB floating IP address
Interface: Port2
Also, 168.63.129.16 is the IP address used for ha communication. You should not do any changes to this IP address like a configure static route.
For traffic consistency, I suggest, you configure source-IP-based persistence on Azure ILB/ELB.
https://learn.microsoft.com/en-us/azure/load-balancer/distribution-mode-concepts
Created on 04-03-2024 06:15 AM Edited on 04-23-2024 12:29 AM
Delete it please
Hello @AliAllafzadeh ,
I suggest, you configure source-IP-based persistence on Azure ILB/ELB.
https://learn.microsoft.com/en-us/azure/load-balancer/distribution-mode-concepts
Can you run this command on both firewalls and try to reach somewhere? Can you share output with us?
diagnose sniffer packet any 'host 192.168.0.x' 4 a ( "x" should be changed with client IP)
Created on 04-04-2024 01:54 AM Edited on 04-23-2024 12:29 AM
Delete it please
Hello @AliAllafzadeh ,
You need to configure 2 routes.
First, configure the route on the route table like this,
Address Prefix: 0.0.0.0/0.0.0.0
Next hop type: Virtual Appliance
Next hop IP: 172.16.136.68
Second, configure the route on Fortigate like this,
Destination : 192.168.0.0/24
Gateway: 172.16.136.65
Device: Port2
Example for azure side
Created on 04-07-2024 11:17 PM Edited on 04-23-2024 12:29 AM
Delete it please
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.