Technical Tip : Local-in Policy not working due to different ip registered location or the physical location of IP addresses
| Description | This article describes an issue when using a local-in policy to block a certain region address but not working as expected. |
| Scope | FortiGate. |
| Solution | Refer to the local-in policy configure below ;
Suppose the blocking should work, but due to differences in registration and physical address location, the access still working.
Example:
diagnose firewall ipgeo ip2country 62.233.39.35
The registration address is Russia but the physical location is Netherlands. The respective address (Netherlands) also needs to be added to the source address since the GeoIP-match. It was only supported on normal firewall policy, not local-in-policy.
Related articles: Technical Tip: Commands to verify GeoIP information and troubleshoot GeoIP database Technical Tip: Registered location and physical location of IP addresses |