![]() The loopback interface guarantees the Firebox can be contacted when there are multiple paths to the dynamic routing peer. In the dynamic routing configuration, use the loopback interface IP address, not the interface name. In the dynamic routing configuration, use the loopback interface IP address instead of a physical interface IP address. The IP address is added to the Secondary Networks list.Īfter you configure the loopback interface, you can use it for dynamic routing. In the IP Address text box, type the IPv4 network IP address to add.The Add a secondary network dialog box appears. To add a secondary IP address to the loopback interface:.In the IP Address text box, type the IPv4 address and subnet mask. ![]() ![]() (Optional) In the Interface Description text box type a description for this interface.To configure the primary loopback interface IP address:.You must configure the loopback interface in the network settings before you can use it in the dynamic routing configuration. 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. The loopback interface is supported in routed mode only. In the loopback interface configuration, you can specify a primary IPv4 address, and you can add secondary networks. 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. You can use the loopback interface for dynamic routing to multiple ISPs when your Firebox is configured with multi-WAN. 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.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |