# config firewall address edit 'restriction_poland' set type geography set country 'PL' Addresses, select 'Create new', select the address Type as 'Geography' and select the country to allow. Im trying out Fortigate VM64-AZURE on Azure. Also make sure your Fortigate SSL VPN config includes 10.1.0.0/23 as part of the internal network (include it with the subnets for your 3 main sites). In this case, you have 3 options create a new VNETor cancel the deployment or delete all the existing VPN Connectoins and Gateway Subnet This is something new. The End user is getting lots of failed VPN login attempts lately, so they created a policy to block traffic from an address group that contains some countries, then created a deny policy (please see cover image), but they are still seeing login attempts from these countries.Īny idea if the configuration is correct (incoming/outgoing interface)?īy default, SSL VPN’s are accessible to all public addresses on internet.ġ) Configure firewall address with the type geography. Remote users go direct how via VPN or not For option 1 make sure you have included the SSL pool 10.1.254.0 in the main site network definitions on the S2S vpn to azure (on both sides).

Fortinet End user reports Geo-Blocking by country doesn't seem to be working. Fortigate in the cloud is severely performance limited.

Fortinet vpn client in azure vm