Router (computing)

This article is about the network device. For the woodworking tool, see Router (woodworking).

Rack containing a service-provider–class router connected to multiple networks

A home–class router with wireless capabilities; many home routers like this example combine router, wireless access point, switch and modem into one single unit (see also residential gateway)

A router ^[a] is a computer and networking device that forwards data packets between computer networks, including internetworks such as the global Internet. ^{[2] [3] [4]}

A router is connected to two or more data lines from different IP networks. When a data packet comes in on a line, the router reads the network address information in the packet header to determine the ultimate destination. Then, using information in its routing table or routing policy, it directs the packet to the next network on its journey. Data packets are forwarded from one router to another through an internetwork until it reaches its destination node. ^[5]

The most familiar type of IP routers are home and small office routers that forward IP packets between the home computers and the Internet. More sophisticated routers, such as enterprise routers, connect large business or ISP networks to powerful core routers that forward data at high speed along the optical fiber lines of the Internet backbone.

Routers can be built from standard computer parts but are mostly specialized purpose-built computers. Early routers used software-based forwarding, running on a CPU. More sophisticated devices use application-specific integrated circuits (ASICs) to increase performance or add advanced filtering and firewall functionality.

Operation

When multiple routers are used in interconnected networks, the routers can exchange information about destination addresses using a routing protocol. Each router builds up a routing table, a list of routes, between two computer systems on the interconnected networks. ^{[6] [7]}

The software that runs the router is composed of two functional processing units that operate simultaneously, called planes: ^[8]

• Control plane: A router maintains a routing table that lists which route should be used to forward a data packet, and through which physical interface connection. It does this using internal pre-configured directives, called static routes, or by learning routes dynamically using a routing protocol. Static and dynamic routes are stored in the routing table. The control-plane logic then strips non-essential directives from the table and builds a forwarding information base (FIB) to be used by the forwarding plane.
• Forwarding plane: This unit forwards the data packets between incoming and outgoing interface connections. It reads the header of each packet as it comes in, matches the destination to entries in the FIB supplied by the control plane, and directs the packet to the outgoing network specified in the FIB.

Applications

A home or small office DSL router showing the telephone socket (left, white) to connect it to the internet using ADSL, and Ethernet jacks (right, yellow) to connect it to home computers and printers.

A carrier class router with 10G/40G/100G interfaces and redundant processor/power/fan modules

A router may have interfaces for multiple types of physical layer connections, such as copper cables, fiber optic, or wireless transmission. It can also support multiple network layer transmission standards. Each network interface is used to enable data packets to be forwarded from one transmission system to another. Routers may also be used to connect two or more logical groups of computer devices known as subnets, each with a unique network prefix.

Routers may provide connectivity within enterprises, between enterprises and the Internet, or between internet service providers' (ISPs') networks, they are also responsible for directing data between different networks. ^[9] The largest routers (such as the Cisco CRS-1 or Juniper PTX) interconnect the various ISPs, or may be used in large enterprise networks. ^[10] Smaller routers usually provide connectivity for typical home and office networks.

All sizes of routers may be found inside enterprises. ^[11] The most powerful routers are usually found in ISPs, academic and research facilities. Large businesses may also need more powerful routers to cope with ever-increasing demands of intranet data traffic. A hierarchical internetworking model for interconnecting routers in large networks is in common use. ^[12] Some routers can connect to Data service units for T1 connections ^{[13] [14] [15]} via serial ports. ^{[16] [17]}

Access, core and distribution

A screenshot of the LuCI web interface used by OpenWrt. This page configures Dynamic DNS.

The hierarchical internetworking model divides enterprise networks into three layers: core, distribution, and access.

Access routers, including small office/home office (SOHO) models, are located at home and customer sites such as branch offices that do not need hierarchical routing of their own. Typically, they are optimized for low cost. Some SOHO routers are capable of running alternative free Linux-based firmware like Tomato, OpenWrt, or DD-WRT. ^[18]

Distribution routers aggregate traffic from multiple access routers. Distribution routers are often responsible for enforcing quality of service across a wide area network (WAN), so they may have considerable memory installed, multiple WAN interface connections, and substantial onboard data processing routines. They may also provide connectivity to groups of file servers or other external networks. ^[19]

In enterprises, a core router may provide a collapsed backbone interconnecting the distribution tier routers from multiple buildings of a campus, or large enterprise locations. They tend to be optimized for high bandwidth but lack some of the features of edge routers. ^[20]

Security

External networks must be carefully considered as part of the overall security strategy of the local network. A router may include a firewall, VPN handling, and other security functions, or they may be handled by separate devices. Routers also commonly perform network address translation which restricts connections initiated from external connections but is not recognized as a security feature by all experts. ^[21] Some experts argue that open source routers are more secure and reliable than closed source routers because errors and potentially exploitable vulnerabilities are more likely to be discovered and addressed in an open-source environment. ^{[22] [23]}

Routing different networks

Routers are also often distinguished on the basis of the network in which they operate. A router in a local area network (LAN) of a single organization is called an interior router. A router that is operated in the Internet backbone is described as exterior router. While a router that connects a LAN with the Internet or a wide area network (WAN) is called a border router, or gateway router . ^[24]

Internet connectivity and internal use

Routers intended for ISP and major enterprise connectivity usually exchange routing information using the Border Gateway Protocol (BGP). RFC   4098 defines the types of BGP routers according to their functions: ^[25]

• Edge router or inter-AS border router: Placed at the edge of an ISP network, where the router is used to peer with the upstream IP transit providers, bilateral peers through IXP, private peering (or even settlement-free peering) through Private Network Interconnect (PNI) via the extensive use of Exterior Border Gateway Protocol (eBGP). ^[26]
• Provider Router (P): A Provider router is also called a transit-router, it sits in an MPLS network and is responsible for establishing label-switched paths between the PE routers. ^[27]
• Provider edge router (PE): An MPLS-specific router in the network's access layer that interconnects with customer edge routers to provide layer 2 or layer 3 VPN services. ^[27]
• Customer edge router (CE): Located at the edge of the subscriber's network, it interconnects with the PE router for L2VPN services, or direct layer 3 IP hand-off in the case of Dedicated Internet Access, if IP Transit services are provided through an MPLS core, the CE peers with the PE using eBGP with the public ASNs of each respective network. In the case of L3VPN services the CE can exchange routes with the PE using eBGP. It is commonly used in both service provider and enterprise or data center organizations. ^[27]
• Core router: Resides within an Autonomous System as a backbone to carry traffic between edge routers. ^[28]
• Within an ISP: In the ISP's autonomous system, a router uses internal BGP to communicate with other ISP edge routers, other intranet core routers, or the ISP's intranet provider border routers.
• Internet backbone: The Internet no longer has a clearly identifiable backbone, unlike its predecessor networks. See default-free zone (DFZ). The major ISPs' system routers make up what could be considered to be the current Internet backbone core. ^[29] ISPs operate all four types of the BGP routers described here. An ISP core router is used to interconnect its edge and border routers. Core routers may also have specialized functions in virtual private networks based on a combination of BGP and Multiprotocol Label Switching protocols. ^[30]
• Port forwarding: In some networks, that rely on legacy IPv4 and NAT, routers (often labeled as NAT boxes) are also used for port forwarding configuration between RFC1918 address space and their publicly assigned IPv4 address. ^[11]
• Voice, data, fax, and video processing routers: Commonly referred to as access servers or gateways, these devices are used to route and process voice, data, video and fax traffic on the Internet. Since 2005, most long-distance phone calls have been processed as IP traffic (VOIP) through a voice gateway. Use of access server-type routers expanded with the advent of the Internet, first with dial-up access and another resurgence with voice phone service.
• Larger networks commonly use multilayer switches, with layer-3 devices being used to simply interconnect multiple subnets within the same security zone, and higher-layer switches when filtering, translation, load balancing, or other higher-level functions are required, especially between zones.

Wi-Fi routers

Main article: Wireless router

Wi-Fi routers combine the functions of a router with those of a wireless access point. They are typically devices with a small form factor, operating on the standard electric power supply for residential use. Connected to the Internet as offered by an Internet service provider, they provide Internet access through a wireless network for home or office use.

History

The first ARPANET router, the Interface Message Processor, was delivered to UCLA August 30, 1969, and went online October 29, 1969.

The concepts of a switching node using software and an interface computer were first proposed by Donald Davies for the NPL network in 1966. ^{[31] [32] [33]} The same idea was conceived by Wesley Clark the following year for use in the ARPANET, which were named Interface Message Processors (IMPs). ^[34] The first interface computer was implemented at the National Physical Laboratory in the United Kingdom in early 1969, followed later that year by the IMPs at the University of California, Los Angeles, the Stanford Research Institute, the University of California, Santa Barbara, and the University of Utah School of Computing in the United States. ^{[35] [36] [37] [38]} All were built with the Honeywell 516. These computers had fundamentally the same functionality as a router does today.

The idea for a router (called a gateway at the time) initially came about through an international group of computer networking researchers called the International Network Working Group (INWG). ^[39] These gateway devices were different from most previous packet switching schemes in two ways. First, they connected dissimilar kinds of networks, such as serial lines and local area networks. Second, they were connectionless devices, which had no role in assuring that traffic was delivered reliably, leaving that function entirely to the hosts. ^[40] This particular idea, the end-to-end principle, was pioneered in the CYCLADES network. ^[41]

The idea was explored in more detail, with the intention to produce a prototype system as part of two contemporaneous programs. One was a program at Xerox PARC to explore new networking technologies, which produced the PARC Universal Packet system. Some time after early 1974, the first Xerox routers became operational. Due to corporate intellectual property concerns, it received little attention outside Xerox for years. ^[42] The other was the DARPA-initiated program, which created the TCP/IP architecture in use today. ^[43] The first true IP router was developed by Ginny Travers at BBN, as part of that DARPA-initiated effort, during 1975–1976. ^{[44] [45]} By the end of 1976, three PDP-11-based routers were in service in the experimental prototype Internet. ^[46] Mike Brecia, Ginny Travers, and Bob Hinden received the IEEE Internet Award for early IP routers in 2008. ^[47]

The first multiprotocol routers were independently created by staff researchers at MIT and Stanford in 1981 and both were also based on PDP-11s. Stanford's router program was led by William Yeager and MIT's by Noel Chiappa. ^{[48] [49] [50] [51]} Virtually all networking now uses TCP/IP, but multiprotocol routers are still manufactured. They were important in the early stages of the growth of computer networking when protocols other than TCP/IP were in use. Modern routers that handle both IPv4 and IPv6 are multiprotocol but are simpler devices than ones processing AppleTalk, DECnet, IPX, and Xerox protocols.

From the mid-1970s and in the 1980s, general-purpose minicomputers served as routers. Modern high-speed routers are network processors or highly specialized computers with extra hardware acceleration added to speed both common routing functions, such as packet forwarding, and specialized functions such as IPsec encryption. There is substantial use of Linux and Unix software-based machines, running open source routing code, for research and other applications. The Cisco IOS operating system was independently designed. Major router operating systems, such as Junos and NX-OS, are extensively modified versions of Unix software.

Forwarding

Further information: Routing and IP routing

The main purpose of a router is to connect multiple networks and forward packets destined either for directly attached networks or more remote networks. A router is considered a layer-3 device because its primary forwarding decision is based on the information in the layer-3 IP packet, specifically the destination IP address. When a router receives a packet, it searches its routing table to find the best match between the destination IP address of the packet and one of the addresses in the routing table. Once a match is found, the packet is encapsulated in the layer-2 data link frame for the outgoing interface indicated in the table entry. A router typically does not look into the packet payload, ^[52] but only at the layer-3 addresses to make a forwarding decision, plus optionally other information in the header for hints on, for example, quality of service (QoS). For pure IP forwarding, a router is designed to minimize the state information associated with individual packets. ^[53] Once a packet is forwarded, the router does not retain any historical information about the packet. ^[b]

The routing table itself can contain information derived from a variety of sources, such as a default or static routes that are configured manually, or dynamic entries from routing protocols where the router learns routes from other routers. A default route is one that is used to route all traffic whose destination does not otherwise appear in the routing table; it is common – even necessary – in small networks, such as a home or small business where the default route simply sends all non-local traffic to the Internet service provider. The default route can be manually configured (as a static route); learned by dynamic routing protocols; or be obtained by DHCP. ^{[c] [54]}

A router can run more than one routing protocol at a time, particularly if it serves as an autonomous system border router between parts of a network that run different routing protocols; if it does so, then redistribution may be used (usually selectively) to share information between the different protocols running on the same router. ^[55]

Besides deciding to which interface a packet is forwarded, which is handled primarily via the routing table, a router also has to manage congestion when packets arrive at a rate higher than the router can process. Three policies commonly used are tail drop, random early detection (RED), and weighted random early detection (WRED). Tail drop is the simplest and most easily implemented: the router simply drops new incoming packets once buffer space in the router is exhausted. RED probabilistically drops datagrams early when the queue exceeds a pre-configured portion of the buffer, until reaching a pre-determined maximum, when it drops all incoming packets, thus reverting to tail drop. WRED can be configured to drop packets more readily dependent on the type of traffic.

Another function a router performs is traffic classification and deciding which packet should be processed first. This is managed through QoS, which is critical when Voice over IP is deployed, so as not to introduce excessive latency. ^[56]

Yet another function a router performs is called policy-based routing where special rules are constructed to override the rules derived from the routing table when a packet forwarding decision is made. ^[57]

Some of the functions may be performed through an application-specific integrated circuit (ASIC) to avoid the overhead of scheduling CPU time to process the packets. Others may have to be performed through the CPU as these packets need special attention that cannot be handled by an ASIC. ^[58]

See also

• Mobile broadband modem
• Modem
• Residential gateway
• Switch virtual interface
• Wireless router

Notes

1. Pronounced /ˈruːtər/ in British English, /ˈraʊtər/ in American and Australian English. ^[1]
2. In some router implementations, the forwarding action can increment a counter associated with the routing table entry for the collection of statistical data.
3. A router can serve as a DHCP client or as a DHCP server.

References

1. "router" . Oxford English Dictionary (Online ed.). Oxford University Press.(Subscription or participating institution membership required.)
2. "A Router is a Computer". Cisco Network Academy. Archived from the original on 2022-07-05.
3. Medhi, Deepankar; Ramasamy, Karthik (2007). Network Routing: Algorithms, Protocols, and Architectures. Elsevier. p. 19. ISBN   9780120885886.
4. Kundu, Sudakshina (2009). Fundamentals of Computer Networks, 2nd Ed. New Delhi: PHI Learning. pp. 85–86, 124. ISBN   9788120334526.
5. "Overview Of Key Routing Protocol Concepts: Architectures, Protocol Types, Algorithms and Metrics". Tcpipguide.com. Archived from the original on 20 December 2010. Retrieved 15 January 2011.
6. "Cisco Networking Academy's Introduction to Routing Dynamically". Cisco. Archived from the original on October 27, 2015. Retrieved August 1, 2015.
7. "What Is Routing?". Cisco. 2022-04-10. Retrieved 2024-03-25. Routing tables can be created manually and "learned" by software as it observes network traffic, or they can be built according to routing protocols.
8. H. Khosravi & T. Anderson (November 2003). Requirements for Separation of IP Control and Forwarding. doi: 10.17487/RFC3654 . RFC 3654.
9. "Which networking component is responsible for directing data between different networks - ITEagers". ITEagers. Retrieved 2024-02-27.
10. "Setting uo Netflow on Cisco Routers". MY-Technet.com date unknown. Archived from the original on 14 July 2011. Retrieved 15 January 2011.
11. "Windows Home Server: Router Setup". Microsoft Technet 14 Aug 2010. Archived from the original on 22 December 2010. Retrieved 15 January 2011.
12. Oppenheimer, Pr (2004). Top-Down Network Design. Indianapolis: Cisco Press. ISBN   978-1-58705-152-4.
13. Beasley, Jeffrey S.; Nilkaew, Piyasat (5 November 2012). A Practical Guide to Advanced Networking. Pearson Education. ISBN   978-0-13-335400-3.
14. Lawson, Wayne (8 February 2001). Configuring Cisco AVVID. Elsevier. ISBN   978-0-08-047673-5.
15. "Computerworld". 23 January 1995.
16. "Serial Interface Cards".
17. "Serial Network Modules".
18. "SOHO Network Requirements Planning and Implementation". ExamCollection. Retrieved 2021-03-25.
19. "How Do WiFi Extenders Work? Repeater, Booster, Extender?". ISP Family. 2021-02-25. Retrieved 2021-03-25.
20. "Hierarchical Network Design Overview (1.1) > Cisco Networking Academy Connecting Networks Companion Guide: Hierarchical Network Design | Cisco Press". www.ciscopress.com. Retrieved 2021-03-21.
21. "Security Considerations Of NAT" (PDF). University of Michigan. Archived from the original (PDF) on October 18, 2014.
22. "Global Internet Experts Reveal Plan for More Secure, Reliable Wi-Fi Routers - and Internet" (Press release). 14 October 2015. Archived from the original on 2015-10-20.
23. "Is Open Source Software More Secure than Proprietary Products?". GovTech. 2010-07-26. Retrieved 2024-03-30.
24. Tamara Dean (2009). Network+ Guide to Networks. Cengage Learning. p. 272. ISBN   9781423902454.
25. H. Berkowitz; et al. (June 2005). Terminology for Benchmarking BGP Device Convergence in the Control Plane. doi: 10.17487/RFC4098 . RFC 4098.
26. "What is the primary role of a router placed at the edge of an ISP network engaging in peering with upstream IP transit providers through eBGP - ITEagers". ITEagers. Retrieved 2024-02-27.
27. Rekhter, Yakov; Rosen, Eric C. (February 2006). BGP/MPLS IP Virtual Private Networks (VPNs) (Report). Internet Engineering Task Force.
28. "M160 Internet Backbone Router" (PDF). Juniper Networks. Archived (PDF) from the original on 20 September 2011. Retrieved 15 January 2011.
29. "Virtual Backbone Routers" (PDF). IronBridge Networks, Inc. September, 2000. Archived (PDF) from the original on 16 July 2011. Retrieved 15 January 2011.
30. E. Rosen; Y. Rekhter (April 2004). BGP/MPLS VPNs.
31. Davies, D. W. (1966). "Proposal for a Digital Communication Network" (PDF).
32. Roberts, Dr. Lawrence G. (May 1995). "The ARPANET & Computer Networks". Archived from the original on 24 March 2016. Retrieved 13 April 2016. Then in June 1966, Davies wrote a second internal paper, "Proposal for a Digital Communication Network" In which he coined the word packet,- a small sub part of the message the user wants to send, and also introduced the concept of an interface computer to sit between the user equipment and the packet network.
33. Pelkey, James (2007). Entrepreneurial Capitalism & Innovation: A History of Computer Communications 1968 - 1988 . Retrieved 2020-02-18. paper dated June 1966 ... introduced the concept of an "interface computer" to sit between the user equipment and the packet network.
34. Pelkey, James. "4.7 Planning the ARPANET: 1967-1968 in Chapter 4 - Networking: Vision and Packet Switching 1959 - 1968". The History of Computer Communications. Archived from the original on December 23, 2022. Retrieved May 9, 2023.
35. John S, Quarterman; Josiah C, Hoskins (1986). "Notable computer networks". Communications of the ACM. 29 (10): 932–971. doi: 10.1145/6617.6618 . S2CID   25341056. The first packet-switching network was implemented at the National Physical Laboratories in the United Kingdom. It was quickly followed by the ARPANET in 1969.
36. Scantlebury, Roger (2001). A Brief History of the NPL Network. Symposium of the Institution of Analysts & Programmers 2001. Archived from the original on 2003-08-07. Retrieved 2024-06-13. The system first went 'live' early in 1969
37. Haughney Dare-Bryan, Christine (June 22, 2023). Computer Freaks (Podcast). Chapter Two: In the Air. Inc. Magazine. 35:55 minutes in. Leonard Kleinrock: Donald Davies ... did make a single node packet switch before ARPA did
38. Hempstead, C.; Worthington, W., eds. (2005). Encyclopedia of 20th-Century Technology. Routledge. pp. 573–5. ISBN   9781135455514 . Retrieved 2015-08-15.
39. Davies, Shanks, Heart, Barker, Despres, Detwiler and Riml, "Report of Subgroup 1 on Communication System", INWG Note No. 1.
40. Edmondson-Yurkanan, Chris (2007). "SIGCOMM's archaeological journey into networking's past". Communications of the ACM. 50 (5): 63–68. doi:10.1145/1230819.1230840. ISSN   0001-0782. INWG#1: Report of Subgroup 1 on Communication System Requirements by Davies, Shanks, Heart, Barker, Despres, Detwiler, and Riml. They wrote: "It was agreed that interworkingbetween packet switching networks should not add complications to the hosts, considering that networks will probably be different and thus gateways between networks will be required. These gateways should be as uncomplicated as possible, whilst allowing as much freedom as possible for the design of individual networks". INWG#1 clarified that gateways and simplicity were accepted concepts when INWG was formed.
41. Bennett, Richard (September 2009). "Designed for Change: End-to-End Arguments, Internet Innovation, and the Net Neutrality Debate" (PDF). Information Technology and Innovation Foundation. pp. 7, 11. Retrieved 11 September 2017.
42. David Boggs, John Shoch, Edward Taft, Robert Metcalfe, "Pup: An Internetwork Architecture", IEEE Transactions on Communications, Volume 28, Issue 4, April 1980, pp. 612- 624.
43. Vinton Cerf, Robert Kahn, "A Protocol for Packet Network Intercommunication", IEEE Transactions on Communications, Volume 22, Issue 5, May 1974, pp. 637 - 648.
44. "Virginia Travers". Internet Hall of Fame. Retrieved 2024-06-16.
45. "Ms. Ginny Strazisar". IT History Society. 21 December 2015. Archived from the original on 1 December 2017. Retrieved 21 November 2017.
46. Craig Partridge, S. Blumenthal, "Data networking at BBN"; IEEE Annals of the History of Computing, Volume 28, Issue 1; January–March 2006.
47. "IEEE INTERNET AWARD RECIPIENTS" (PDF).
48. Valley of the Nerds: Who Really Invented the Multiprotocol Router, and Why Should We Care? Archived 2016-03-03 at the Wayback Machine , Public Broadcasting Service, Accessed August 11, 2007.
49. Router Man Archived 2013-06-05 at the Wayback Machine , NetworkWorld, Accessed June 22, 2007.
50. David D. Clark, "M.I.T. Campus Network Implementation", CCNG-2, Campus Computer Network Group, M.I.T., Cambridge, 1982; pp. 26.
51. Pete Carey, "A Start-Up's True Tale: Often-told story of Cisco's launch leaves out the drama, intrigue", San Jose Mercury News, December 1, 2001.
52. "Packet Forwarding and Routing on IPv4 Networks - System Administration Guide: IP Services". docs.oracle.com. Retrieved 2021-03-25.
53. Roberts, Lawrence (22 July 2003). "The Next Generation of IP - Flow Routing". Archived from the original on 4 April 2015. Retrieved 22 February 2015.
54. David Davis (April 19, 2007). "Cisco administration 101: What you need to know about default routes". Archived from the original on June 25, 2014. Retrieved June 5, 2014.
55. Diane Teare (March 2013). Implementing Cisco IP Routing (ROUTE): Foundation Learning Guide. Cisco Press. pp. 330–334.
56. Donahue, Gary A. (2007-06-21). Network Warrior. "O'Reilly Media, Inc.". ISBN   978-0-596-10151-0.
57. Diane Teare (March 2013). "Chapter 5: Implementing Path Control". Implementing Cisco IP-Routing (ROUTE): Foundation Learning Guide. Cisco Press. pp. 330–334.
58. Schudel, Gregg; Smith, David (2007-12-29). Router Security Strategies: Securing IP Network Traffic Planes. Pearson Education. ISBN   978-0-13-279673-6.