Multiple routing tables

We can configure a specific set of routes for each IP configured on the appliance. This setting can overcome a single point of failure that occurs from having a single interface and gateway for a particular subnet, or from having a single default gateway.

Interface-specific routes might also be required to solve some firewall conflicts. In an appliance that has multiple interfaces, the return path for a particular request might be different from the request path. In certain firewall configurations, this situation is seen as a spoofing attack and the packet is discarded.

For example, if the appliance has an IP of 172.16.197.11/24 configured on Interface 1.2 and a gateway at 172.16.197.2, then select the table for IP 172.16.197.11 and add the following two static routes:

If a set of static routes is not provided for a particular IP's table, or the static routes in the IP's table do not result in a route for the IP, then the “Default” static route table is applied.

If the ability to define different routes for different destination IP address is not required, then place all required static routes under the “Default” static route table. This is also where migrated static routes from prior releases that do not provide this feature are placed.

Parent topic: Configure static routes