Routers

With source route bridging two frame types are used in order to find the route to the destination network segment. Single-Route (SR) frames comprise most of the network traffic and have set destinations, while All-Route(AR) frames are used to find routes. Bridges send AR frames by broadcasting on all network branches; each step of the followed route is registered by the bridge performing it. Each frame has a maximum hop count, which is determined to be greater than the diameter of the network graph, and is decremented by each bridge. Frames are dropped when this hop count reaches zero, to avoid indefinite looping of AR frames. The first AR frame which reaches its destination is considered to have followed the best route, and the route can be used for subsequent SR frames; the other AR frames are discarded. This method of locating a destination network can allow for indirect load balancing among multiple bridges connecting two networks. The more a bridge is loaded, the less likely it is to take part in the route finding process for a new destination as it will be slow to forward packets. A new AR packet will find a different route over a less busy path if one exists. This method is very different from transparent bridge usage, where redundant bridges will be inactivated; however, more overhead is introduced to find routes, and space is wasted to store them in frames. A switch with a faster backplane can be just as good for performance, if not for fault tolerance.

This method uses a forwarding database to send frames across network segments. The forwarding database is initially empty and entries in the database are built as the bridge receives frames. If an address entry is not found in the forwarding database, the frame is rebroadcast to all ports of the bridge, forwarding the frame to all segments except the source address. By means of these broadcast frames, the destination network will respond and a route will be created. Along with recording the network segment to which a particular frame is to be sent, bridges may also record a bandwidth metric to avoid looping when multiple paths are available. Devices that have this transparent bridging functionality are also known as adaptive bridges.

A network bridge connects multiple network segments at the data link layer (layer 2) of the OSI model, and the term layer 2 switch is often used interchangeably with bridge. Bridges are similar to repeaters or network hubs, devices that connect network segments at the physical layer, however a bridge works by using bridging where traffic from one network is managed rather than simply rebroadcast to adjacent network segments. In Ethernet networks, the term “bridge” formally means a device that behaves according to the IEEE 802.1D standard—this is most often referred to as a network switch in marketing literature.

Since bridging takes place at the data link layer of the OSI model, a bridge processes the information from each frame of data it receives. In an Ethernet frame, this provides the MAC address of the frame’s source and destination. Bridges use two methods to resolve the network segment that a MAC address belongs to.

In computer networking and telecommunications, route flapping occurs when a router alternately advertises a destination network via one route then another (or as unavailable, and then available again) in quick sequence.Route flapping is caused by pathological conditions (hardware errors, software errors, configuration errors, unreliable connections, etc.) within the network which cause certain reachability information to be repeatedly advertised and withdrawn. The most common causes of route flapping are configuration errors and intermittent errors in communications links. Route flapping often forces a router to recalculate a new or preferred route to a particular network, while traffic destined for that network is in transit through the router.

One IEEE 802.11 WAP can typically communicate with 30 client systems located within a radius of 100 m. However, the actual range of communication can vary significantly, depending on such variables as indoor or outdoor placement, height above ground, nearby obstructions, other electronic devices that might actively interfere with the signal by broadcasting on the same frequency, type of antenna, the current weather, operating radio frequency, and the power output of devices. Network designers can extend the range of WAPs through the use of repeaters and reflectors, which can bounce or amplify radio signals that ordinarily would go un-received. In experimental conditions, wireless networking has operated over distances of several kilometers.

Most jurisdictions have only a limited number of frequencies legally available for use by wireless networks. Usually, adjacent WAPs will use different frequencies to communicate with their clients in order to avoid interference between the two nearby systems. But wireless devices can “listen” for data traffic on other frequencies, and can rapidly switch from one frequency to another to achieve better reception on a different WAP. However, the limited number of frequencies becomes problematic in crowded downtown areas with tall buildings housing multiple WAPs, when overlap causes interference.

Wireless networking lags behind wired networking in terms of increasing bandwidth and throughput. While (as of 2004) typical wireless devices for the consumer market can reach speeds of 11 Mbit/s (megabits per second) (IEEE 802.11b) or 54 Mbit/s (IEEE 802.11a, IEEE 802.11g), wired hardware of similar cost reaches 1000 Mbit/s (Gigabit Ethernet). One impediment to increasing the speed of wireless communications comes from Wi-Fi’s use of a shared communications medium, so a WAP is only able to use somewhat less than half the actual over-the-air rate for data throughput. Thus a typical 54 MBit/s wireless connection actually carries TCP/IP data at 20 to 25 Mbit/s. Users of legacy wired networks expect the faster speeds, and people using wireless connections keenly want to see the wireless networks catch up.

As of 2006 a new standard for wireless, 802.11n is awaiting final certification from IEEE. This new standard operates at speeds up to 540 Mbit/s and at longer distances (~50 m) than 802.11g. Use of legacy wired networks (especially in consumer applications) is expected to decline sharply as the common 100 Mbit/s speed is surpassed and users no longer need to worry about running wires to attain high bandwidth.

Interference can commonly cause problems with wireless networking reception, as many devices operate using the 2.4 GHz ISM band. A nearby wireless phone or anything with greater transmission power within close proximity can markedly reduce the perceived signal strength of a wireless access point. Microwave ovens are also known to interfere with wireless networks.

In computer networking, a wireless access point (WAP or AP) is a device that connects wireless communication devices together to form a wireless network. The WAP usually connects to a wired network, and can relay data between wireless devices and wired devices. Several WAPs can link together to form a larger network that allows “roaming”. (In contrast, a network where the client devices manage themselves - without the need for any access points - becomes an ad-hoc network.) WAPs have IP addresses for configuration.Low-cost and easily-installed Wi-Fi WAPs grew rapidly in popularity in the early 2000s. These devices offered a way to avoid the tangled messes of category 5 cable associated with typical Ethernet networks of the day. Whereas wiring a business, home, or school often requires stringing many cables through walls and ceilings, wireless networking allows connecting with few or no new cables. Wireless networks also allow greater mobility, freeing users from the restrictions of using a computer cabled to the wall. In the industrial and commercial contexts, wireless networking has had a big impact on operations: employees in these areas now often carry portable data terminals integrating barcode scanners and wireless links, allowing them to update work in progress and inventory in real-time. At home with a residential gateway, any convenient chair or lawn becomes a desk for the laptop.

A typical corporate use involves attaching several WAPs to a wired network and then providing wireless access to the office LAN. Within the range of the WAPs, the wireless end user has a full network connection with the benefit of mobility. In this instance, the WAP functions as a gateway for clients to access the wired network. Another use involves bridging two wired networks in conditions inappropriate for cable: for example, a manufacturer can wirelessly connect a remote warehouse’s wired network with a separate (though within line of sight) office’s wired network.

Another wireless topology, a lily-pad network, consists of a series of access points spread over a large area, each connected to a different network. This provides hot spots where wireless clients can connect to the Internet without regard for the particular networks to which they have attached for the moment. The concept can become organic in large cities, where a combination of coffeehouses, libraries, other public spaces offering wireless access, as well as privately owned open access points, allow clients to roam over a large area (like hopping from lily pad to lily pad), staying more or less continuously connected.

Home wireless networks, the majority, generally have only one WAP to connect all the computers in a home. Most are wireless routers, meaning converged devices that include a WAP, Ethernet router, and often a switch in the same package. Many also converge a broadband modem. Most owners leave their encryption settings at default, hence neighbors can use them. In places where most homes have their own WAP within range of the neighbors’ WAP, it’s possible for technically savvy people to turn off their encryption and set up a wireless community network, creating an intra-city communication network without the need of wired networks.

A WAP may also act as the network’s arbitrator, negotiating when each nearby client device can transmit. However, the vast majority of currently installed IEEE 802.11 networks do not implement this, using a distributed pseudo-random algorithm instead.

The very first device that had fundamentally the same functionality as a router does today, i.e a packet switch, was the Interface Message Processor (IMP); IMPs were the devices that made up the ARPANET, the first packet switching network. The idea for a router (although they were called “gateways” at the time) initially came about through an international group of computer networking researchers called the International Network Working Group (INWG). Set up in 1972 as an informal group to consider the technical issues involved in connecting different networks, later that year it became a subcommittee of the International Federation for Information Processing.
These devices were different from most previous packet switches 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 entirely to the hosts (although this particular idea had been previously pioneered in the CYCLADES network).The idea was explored in more detail, with the intention to produce real prototype system, as part of two contemporaneous programs. One was the initial DARPA-initiated program, which created the TCP/IP architecture of today. The other was a program at Xerox PARC to explore new networking technologies, which produced the PARC Universal Packet system, although due to corporate intellectual property concerns it received little attention outside Xerox until years later. [8]

The earliest Xerox routers came into operation sometime after early 1974. The first true IP router was developed by Virginia Strazisar at BBN, as part of that DARPA-initiated effort, during 1975-1976. By the end of 1976, three PDP-11-based routers were in service in the experimental prototype Internet.
The first multiprotocol routers were independently created by staff researchers at MIT and Stanford in 1981; the Stanford router was done by William Yeager, and the MIT one by Noel Chiappa; both were also based on PDP-11s. As virtually all networking now uses IP at the network layer, multiprotocol routers are largely obsolete, although they were important in the early stages of the growth of computer networking, when several protocols other than TCP/IP were in widespread use. Routers that handle both IPv4 and IPv6 arguably are multiprotocol, but in a far less variable sense than a router that processed AppleTalk, DECnet, IP, and Xerox protocols.In the original era of routing (from the mid-1970s through the 1980s), general-purpose mini-computers served as routers. Although general-purpose computers can perform routing, modern high-speed routers are highly specialized computers, generally with extra hardware added to accelerate both common routing functions such as packet forwarding and specialised functions such as IPsec encryption.Still, there is substantial use of Linux and Unix machines, running open source routing code, for routing research and selected other applications. While Cisco’s operating system was independently designed, other major router operating systems, such as those from Juniper Networks and Extreme Networks, are extensively modified but still have Unix ancestry.Other changes also improve reliability, such as redundant control processors with stateful failover, and using storage having no moving parts for program loading. As much reliability comes from operational techniques for running critical routers as it does to the router design itself. It is the best common practice, for example, to use redundant uninterruptible power supplies for all critical network elements, with generator backup for the batteries or flywheels of those power supplies.

Distribution routers aggregate traffic from multiple access routers, either at the same site, or to collect the data streams from multiple sites to a major enterprise location. Distribution routers often are responsible for enforcing quality of service across a WAN, so they may have considerable memory, multiple WAN interfaces, and substantial processing intelligence.

They may also provide connectivity to groups of servers or to external networks. In the latter application, the router’s functionality must be carefully considered as part of the overall security architecture. Separate from the router may be a Firewall or VPN concentrator, or the router may include these and other security functions.

When an enterprise is primarily on one campus, there may not be a distinct distribution tier, other than perhaps off-campus access. In such cases, the access routers, connected to LANs, interconnect via core routers.

Residential gateways (often called routers) are frequently used in homes to connect to a broadband service, such as IP over cable or DSL. A home router may allow connectivity to an enterprise via a secure Virtual Private Network.While functionally similar to routers, residential gateways use network address translation instead of routing. Instead of connecting local computers to the remote network directly, a residential gateway must make local computers appear to be a single computer.

Routers may provide connectivity inside enterprises, between enterprises and the Internet, and inside Internet Service Providers (ISP). The largest routers (for example the Cisco CRS-1 or Juniper T1600) interconnect ISPs, are used inside ISPs, or may be used in very large enterprise networks. An example of an enterprise router would be the Cisco 7600 (pictured above). The smallest routers provide connectivity for small and home offices (for example the Linksys BEFSR41).