Configure Geolocation Exceptions

To identify the geographic location of connections through the Firebox, the Geolocation subscription service uses a database of IP addresses and countries. If there are sites that might be included in the Geolocation database that you want to make sure are never blocked, you can add Geolocation exceptions to your Firebox. Geolocation never blocks connections to or from sites on the exceptions list.

The Geolocation exceptions list is shared by all Geolocation actions. Any changes that you make to the exceptions list when you edit a Geolocation action apply to all Geolocation actions on your Firebox.

When you add a site to any one of the Botnet Detection Exceptions, Geolocation Exceptions, or Blocked Sites Exceptions lists, the site is not blocked by any of these services or Default Packet Handling.

For example, if you add to the Geolocation Exceptions list, then Botnet Detection, Blocked Sites, and Default Packet Handling also do not block the site. If you already added a site to one exception list, you might see an error if you try to add the site to an exception list for another service.

After you configure Geolocation exceptions, you can export the exception list and import it to a different Firebox.

Add Geolocation Exceptions

You can add an exception for an IPv4 or IPv6 host IP address, network address, host range, or FQDN.

Remove Geolocation Exceptions

You can remove Geolocation exceptions that you no longer need.

Import and Export Geolocation Exceptions

You can export the Geolocation exceptions list from one Firebox and import it to a different Firebox. This makes it easy to add the same Geolocation exceptions to all the Fireboxes you manage.

When you import exceptions, you must specify whether to clear the existing exceptions first. If you choose not to clear the list, the imported exceptions are added to the existing exceptions.

See Also

About Geolocation