Static routing: Difference between revisions

Revision as of 11:06, 28 December 2024

Revision as of 14:57, 25 January 2025

Line 1:

{{Short description|Use of fixed routes for routing in networks}}

'''Static routing''' describes a process by which [[routing]] is configured with fixed values whichthat do not change at runtime unless manually edited. Static routes are used with and without dynamic [[Routing protocol]]s and usually share the same [[routing table]] as those protocols.<ref>[http://www.redbooks.ibm.com/redbooks/pdfs/gg243376.pdf TCP/IP Tutorial and Technical Overview (IBM RedBooks Series)]</ref> Routes require at least two attributes; the destination and the gateway, but may contain additional attributes such as a [[Metrics (networking)|metric]] (sometimes called the ''administrative distance''). Some implementations treat the network address and [[subnet mask]] as separate values, however in practice both of the values have to be considered for any given routing decision to determine the [[longest prefix match]]. Static routes together with ''connected'' routes and routes from configuration protocols such as [[DHCP]] or [[Neighbor Discovery Protocol|Router Advertisements]] provide the routes which are then redistributed using dynamic routing protocols.<ref>{{Cite web |title=ESPCommunity |url=https://enterprise-support.nvidia.com/s/article/howto-configure-bgp-on-mellanox-switches |access-date=2024-12-18 |website=enterprise-support.nvidia.com}}</ref> While static routes are entered into the system and remain there until removed or changed manually, dynamic routing protocols create and delete routes dynamically at runtime without intervention. Thus the term ''static'' here refers to the nature of remaining unchanged by the system itself. The most prominent example of a static route is a [[default route]] which is often used on devices with a statically configured [[IP address]] to provide the device with access to the rest of the network or the internet by default.<ref>{{Cite web |title=Static Routing {{!}} Cumulus Linux 5.11 |url=https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-511/Layer-3/Routing/Static-Routing/#configure-a-gateway-or-default-route |access-date=2024-12-18 |website=docs.nvidia.com}}</ref> In contrast to a so called ''connected'' route which is automatically generated upon address assignment based on the used subnet mask, a static route must be manually configured. Due to this the configuration may fail if there is no route to the provided gateway at the time of configuration, other than the connected route which will always succeed as it does not require a gateway. The gateway of a static route need not be an address, but can also specify an interface in most implementations.

== Uses ==

Line 8 ⟶ 9:

* Static routing has applications in environments with many routes with infrequent changes as it reduces the delay it would take to synchronize the routes from another device.

* On heavily resource constrained devices where routing protocols may not be viable due to lack of computation power, static routes may be used instead.

* Static routes, connected routes, and routes from dynamic configuration protocols can be redistributed by dynamic routing protocols. For instance, a router may have a static or connected route for a local network segment, which is then redistributed over dynamic routing protocols to enable connectivity to that network.<ref>{{Cite web |title=Route Filtering and Redistribution {{!}} Cumulus Linux 5.11 |url=https://docs.nvidia.com/networking-ethernet-software/cumulus-linux-511/Layer-3/Routing/Route-Filtering-and-Redistribution/#route-redistribution |access-date=2024-12-18 |website=docs.nvidia.com}}</ref>

* By using the [[Metrics (networking)|metric]] to reduce the priority of a static route a fallback can be provided for instance when a DHCP server becomes unavailable. This can also prevent a type of lockout situation in which one would be unable to access the device otherwise.

Line 14 ⟶ 15:

Static routing has the following advantages:

* Due to being configured on the device it can serve as a bootstrap for other protocols.<ref>{{Cite web |title=Inter-Router Communication > BGP Fundamentals {{!}} Cisco Press |url=https://www.ciscopress.com/articles/article.asp?p=2756480&seqNum=2 |access-date=2024-12-18 |website=www.ciscopress.com}}</ref>

* It does not require connectivity to work, providing high fault- tolerance in case of network failures.

* Compared to dynamic routing protocols, static routes are much more widely available, for instance, many low-end consumer switches are capable of setting static routes.{{cn|date=December 2024}}

* As static routes are not read from the network, there are also fewer security considerations. Dynamic routing protocols may need to be secured such that an attacker cannot redirect traffic from the outside.<ref>{{Cite web |title=IP Routing Configuration Guide, Cisco IOS XE 17.16.x (Catalyst 9500 Switches) - Configuring OSPFv3 Authentication Support with IPsec |url=https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst9500/software/release/17-16/configuration_guide/rtng/b_1716_rtng_9500_cg/configuring_ospfv3_authentication_support_with_ipsec.html |access-date=2024-12-18 |website=Cisco |language=en}}</ref>

Line 22 ⟶ 23:

* '''Human error:''' As the routes have to be manually configured this may be a source of human error in the absence of automated configuration management.

* '''Administrative overhead:''' Similarly the routes have to be provided to the devices. This can be remedied by configuration management, but also using simpler means of using a [[template engine]] to generate configuration using repetition or [[IP address management]] software.

* '''Fault tolerance:''' While static routes not being removed during a network failure can be good in that routes continue to function, however, most implementations continue to use a static route as long as the interface the gateway is on is in an ''up'' state. When [[Failure of electronic components|network hardware fails]] it is not necessary ''down''; a [[Hang (computing)|hang]] may cause interfaces to keep running but not acceptingaccept traffic. Routing protocols usually implement timeouts after which routes are removed, or have integration with additional protocols such as [[Bidirectional Forwarding Detection]] to reduce the time the faulty route is present to sub-second.

* '''Observability:''' Static routes themselves do not propagate, which means that in a network built using only static routes it is hard to get a big picture of all present routes unless [[Event monitoring|monitored]]. Dynamic routing protocols often transmit topology information or can be connected to debugging tools such as a [[Looking Glass server]].

Line 38 ⟶ 39:

=== Cisco ===

[[Cisco Systems|Cisco routers]] running the [[Cisco IOS]] operating system can be configured using the command line interface:<ref>{{Cite web |date=2013-02-02 |title=Cisco IOS IP Command Reference, Volume 2 of 4: Routing Protocols, Release 12.3 T - IP Routing Protocol Commands: ip policy route-map through is-type |url=http://www.cisco.com/en/US/docs/ios/12_3t/ip_route/command/reference/ip2_i2gt.html#wp1106404 |access-date=2024-12-18 |archive-url=https://web.archive.org/web/20130202041013/http://www.cisco.com/en/US/docs/ios/12_3t/ip_route/command/reference/ip2_i2gt.html#wp1106404 |archive-date=2 February 2013 }}</ref>

<syntaxhighlight lang="console">