- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Site 2 Site VPN with Azure
Please help,
I can access On-Prem from Azure but I cannot access Azure from On-Prem from firewall level and LAN behind Firewall.
Azure
172.16.0.0/21 - Address space
172.16.1.0/24 - Subnet
172.16.0.0/24 - GW Subnet
NSG in Azure
ICMP and RDP are Any Any Any Allow
VM in Azure
All firewalls are disabled
On-Prem / Fortigate 60E v6.2.3 build1066 (GA)
PPPoE - WAN
192.168.1.0/24 - LAN
Thank you in advance
- Labels:
-
FortiGate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Please check mtu traffic size from On-prem to Azure.
You can try to lower TCP-MSS on policy that allows traffic to go to Azure
Created on ‎10-06-2022 08:50 AM Edited on ‎10-06-2022 08:55 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi
Here is the result of my firewall MTU
the TCP-MSS on policy, what value should I input?
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Additional info:IPsec Monitor
IPv4 Policy
Ping from Firewall
Tracert from LAN (On-Prem)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What do your route-tables look like in both Azure and on the FTG?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here: Fortinet routing table.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Please give us the output from the below command.
FW # get router info routing-table database
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Everything looks good on the Fortigate. If you can take a screen shot of the route-table(s) on the Azure side that would work. It could be your not propagating the routes to the vNET from the VNG. By default, the VNG will route RFC1918 back down the S-2-S tunnel so if there is no route for the destination subnet in the VNG route-table it will not reach any host that resides there.
Created on ‎10-06-2022 01:56 PM Edited on ‎10-06-2022 02:16 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for confirming the setup from my Fortigate.
Here is the result of the query.
