- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Geo blocking issue for LAN network
Hi Team,
We are facing issue after enabling Geo blocking for other country except India.
Policy which I have configured -
Incoming interface - SDWAN interface
Outgoing Interface - Vlan Interface.
Source country - India
Destination - VIP
NAT - Natted IP (1.1.1.1-100.100.100.1) For example
Policy - Accept
Issue that has been observed - Internal servers are not able to access site - for example - www.xxx.com
which VIP is mapped with this policy
When I enabled source - ALL that time is everything is going on smoothly.
thank you.
Solved! Go to Solution.
- Labels:
-
FortiGate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello team,
I have followed below Geo IP code from documents of Fortigate after that issue has been resolved.
Steps have been taken by as follows:
1. Source country have chosen - India
2. Create one test Geo location added in the policy - Set country ZZ.
Below is the link: for Specials code of Geo IP
ZZ - Reserved (IP addresses that are not assigned, e.g., 10.0.0.0/24)
For more information please refer the below documents.
https://docs.fortinet.com/document/fortiadc/7.4.1/handbook/522244/special-geo-codes
Thank you.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
Is there particular reason why traffic is NATed?
Moreover, you may consider to verify GEO IP category:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
If this policy is used for access from LAN devices as well (~hairpin NAT), you will need to add your local subnets into the list of permitted sources in that policy.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Umesh,
You had another thread with the initial configuration of this as well, so not sure what you ended up with, but:
1: Does this work when you disable this rule?
2: This seems to be a Firewall rule, no a Local In rule, so it will block you other local servers from accessing the server on VirtualIP NAT.
I would:
1: Make sure everything works on a routing level, without this rule enabled.
2: Make internal DNS that points to 'www.xxx.com' on the internal IP - unless you have a Very good reason to access that server via the public IP (making more load on the firewall!)
It would also be helpful to know, if you're setting up a new firewall or this is an existing installation you try to 'harden'.
IT System Admin,
Arp-Hansen Hotrel Group A/S, Copenhagen, DK
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
not resolved the issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello team,
I have followed below Geo IP code from documents of Fortigate after that issue has been resolved.
Steps have been taken by as follows:
1. Source country have chosen - India
2. Create one test Geo location added in the policy - Set country ZZ.
Below is the link: for Specials code of Geo IP
ZZ - Reserved (IP addresses that are not assigned, e.g., 10.0.0.0/24)
For more information please refer the below documents.
https://docs.fortinet.com/document/fortiadc/7.4.1/handbook/522244/special-geo-codes
Thank you.
