Sophos Community
  • User
  • Help
  • Site
  • Search
  • User
  • All Groups
  • Knowledge Base
  • Community Blog
  • Member Recognition
  • More
  • Cancel

Knowledge Base

  • Advisories
  • +CyberoamOS
  • +Data Control and DLP
  • Email Appliance
  • +Endpoint Security and Control
  • +Free Tools
  • +General
  • +Mobile
  • +PureMessage
  • +Reflexion
  • +SafeGuard encryption
  • +Server protection
  • +Sophos Central
  • Sophos Clean
  • Sophos Home
  • +Sophos UTM 9
  • Web Appliance
  • +XG Firewall
Tweets by SophosSupport

Sophos XG Firewall: How to configure a floating static unicast route

  • Article ID: 123611
  • Updated: 30 Oct 2018
  • 0 people found this helpful
  • Available in: English | Español | Italiano | 日本語 | Français | Deutsch

Overview

A floating static unicast route is a low priority route that has a greater Administrative Distance than other dynamic or static routes.

The following sections are covered:

  • Configuration
  • Related information
  • Feedback and contact

Applies to the following Sophos products and versions
Sophos Firewall

Configuration

You must be logged in to the Admin Console as an administrator with Read-Write permissions for the relevant feature(s).

  1. Go to Routing > Static Routing. Under the IPv4 Unicast Route section, click Add to add a new unicast route.
  2. Specify the Destination IP / Netmask, Gateway, Interface, and Distance through which routing will be done. Specify the Distance as greater than that of the other routes. Here, we have set the Distance to 255 (the maximum value allowed).
  3. Click Save to save the configuration.

Note:

  • A floating static route will only take effect when the IP address of an interface is removed or changed to a different network IP.
  • The metric is useful in cases where the IP addresses are obtained dynamically (DHCP or PPPoE).
  • In the following scenario, there are two static routes. One is a floating static route. Both interfaces are not configured with DHCP or PPPoE and in this case, the floating static route will not work as expected.




    Routing table with both the interfaces connected.


    The interface (eth4) where the higher priority static route is pointed to is then unplugged.



    The following routing table shows that the interface was not changed from eth4 to eth5.

Related information

  • Sophos XG Firewall: How to configure multicast routing

Feedback and contact

If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article.
This is invaluable to us to ensure that we continually strive to give our customers the best information possible.

Article appears in the following topics
  • XG Firewall > Sophos Firewall > System > Routing

Did this article provide the information you were looking for?

Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.

  • Submit
Sophos Footer
  • T&Cs
  • Help
  • Cookie Info
  • Contact Support

© 1997 - 2019 Sophos Ltd. All rights reserved.