Configure a Loopback Interface

If your Firebox runs Fireware OS v11.11 or higher, you can enable a loopback interface on your Firebox, which is a virtual interface assigned to the Firebox that is not associated with a specific physical interface. You can use the loopback interface for dynamic routing to multiple ISPs when your Firebox is configured with multi-WAN. A loopback interface can increase the stability of dynamic routing through a multi-WAN connection because it ensures the consistency of the next hop and avoids the potential for BGP routing oscillation.

In the loopback interface configuration, you can specify a primary IPv4 address, and you can add secondary networks. The loopback interface is supported in routed mode only.

You cannot use the loopback interface in policies as the local gateway IP address of a BOVPN or BOVPN virtual interface, or as the destination in a static network route.

You must configure the loopback interface in the network settings before you can use it in the dynamic routing configuration.

After you configure the loopback interface, you can use it for dynamic routing. In the dynamic routing configuration, use the loopback interface IP address instead of a physical interface IP address. In the dynamic routing configuration, use the loopback interface IP address, not the interface name.

The loopback interface guarantees the Firebox can be contacted when there are multiple paths to the dynamic routing peer. Because the loopback interface IP address does not depend on the link status of any interface, it is always up unless the attached router goes down. The loopback IP address and the attached subnets remain in the routing table even if one of the Firebox interfaces goes down. The loopback interface IP address also enables load balancing when multiple paths are available.

Related Topics

Configure IPv4 Routing with OSPF

Configure IPv4 and IPv6 Routing with BGP

Configure IPv4 Routing with RIP