Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Default gateway
open-in-new
<h2 id="role">Role</h2> <p>A <a href="/facts/Gateway_(telecommunications)/YTYSqhqN">gateway</a> is a network node that serves as an access point to another network, often involving not only a change of addressing, but also a different networking technology. More narrowly defined, a router merely forwards packets between networks with different <a href="/facts/IP_address/z9V22Sw9">network prefixes</a>. The networking software stack of each computer contains a <a href="/facts/Routing_table/tufajWvV">routing table</a> that specifies which interface is used for transmission and which router on the network is responsible for forwarding to a specific set of addresses. If none of these forwarding rules is appropriate for a given destination address, the default gateway is chosen as the router of last resort. The default gateway can be specified by the <a href="/facts/Route_(command)/s7u8T2nk">route</a> command to configure the node's routing table and <a href="/facts/Default_route/qEc68cgL">default route</a>. </p><p>In a home or small office environment, the default gateway is a device, such as a <a href="/facts/DSL_router/sgQeFhbD">DSL router</a> or <a href="/facts/Cable_router/X8oXKKj2">cable router</a>, that connects the local network to the Internet. It serves as the default gateway for all network devices. </p><p>Enterprise network systems may require many internal <a href="/facts/Network_segment/D0gAdNdR">network segments</a>. A device wishing to communicate with a host on the public Internet, for example, forwards the packet to the default gateway for its network segment. This router also has a default route configured to a device on an adjacent network, one hop closer to the public network. </p> <h2 id="examples">Examples</h2> <h3>Single router</h3> <p>The following example shows IP addresses that might be used with an office network that consists of six hosts plus a router. The six hosts addresses are: </p> <ul><li>192.168.4.3</li> <li>192.168.4.4</li> <li>192.168.4.5</li> <li>192.168.4.6</li> <li>192.168.4.7</li> <li>192.168.4.8</li></ul> <p>The router's inside address is: </p> <ul><li>192.168.4.1</li></ul> <p>The network has a <a href="/facts/Subnet_mask/s1rQsNDv">subnet mask</a> of: </p> <ul><li>255.255.255.0 (/24 in <a href="/facts/Classless_Inter-Domain_Routing/YU0SEmfp">CIDR</a> notation)</li></ul> <p>The address range assignable to hosts is from 192.168.4.1 to 192.168.4.254. TCP/IP defines the addresses 192.168.4.0 (network ID address) and 192.168.4.255 (broadcast IP address). </p><p>The office's hosts send packets to addresses within this range directly, by resolving the destination IP address into a <a href="/facts/MAC_address/SVcTfgUH">MAC address</a> with the <a href="/facts/Address_Resolution_Protocol/1QyKybkn">Address Resolution Protocol</a> (ARP) sequence and then encapsulates the IP packet into a MAC frame addressed to the destination host. </p><p>A packet addressed outside of this range, for this example, addressed to 192.168.12.3, cannot travel directly to the destination. Instead it must be sent to the default gateway for further routing to their ultimate destination. In this example, the default gateway uses the IP address 192.168.4.1, which is resolved into a MAC address with ARP in the usual way. The destination IP address remains 192.168.12.3, but the next-hop MAC address is that of the gateway, rather than of the ultimate destination. </p> <h3>Multi-router</h3><p> In another example, a network with three routers and three hosts is connected to the Internet through Router1. The hosts' addresses are:</p> <ul><li>PC1 10.1.1.100, default gateway 10.1.1.1</li> <li>PC2 172.16.1.100, default gateway 172.16.1.1</li> <li>PC3 192.168.1.100, default gateway 192.168.1.96</li></ul> <p>Router1: </p> <ul><li>Interface 1 5.5.5.2 (<a href="/facts/Public_IP/z9V22Sw9">public IP</a>)</li> <li>Interface 2 10.1.1.1</li></ul> <p>Router2: </p> <ul><li>Interface 1 10.1.1.2</li> <li>Interface 2 172.16.1.1</li></ul> <p>Router3: </p> <ul><li>Interface 1 10.1.1.3</li> <li>Interface 2 192.168.1.96</li></ul> <p>Network mask in all networks: 255.255.255.0 (/24 in <a href="/facts/Classless_Inter-Domain_Routing/YU0SEmfp">CIDR</a> notation). If the routers do not use a <a href="/facts/Routing_protocol/LH5U2Qh5">routing protocol</a> to discover which network each router is connected to, then the <a href="/facts/Routing_table/tufajWvV">routing table</a> of each router must be set up. </p><p>Router1 </p> <table><tbody><tr><th>Network ID</th><th>Network mask</th><th>Gateway</th><th>Interface (examples; may vary)</th><th>Cost (decreases the <a href="/facts/Time_to_live/CMFdghQh">TTL</a>)</th></tr><tr><td><a href="/facts/0.0.0.0/5DH19BB1">0.0.0.0</a> (<a href="/facts/Default_route/qEc68cgL">default route</a>)</td><td><a href="/facts/0.0.0.0/5DH19BB1">0.0.0.0</a></td><td>Assigned by ISP (e.g., 5.5.5.1)</td><td>eth0 (Ethernet 1st adapter)</td><td>10</td></tr><tr><td>10.1.1.0</td><td>255.255.255.0</td><td>10.1.1.1</td><td>eth1 (Ethernet 2nd adapter)</td><td>10</td></tr><tr><td>172.16.1.0</td><td>255.255.255.0</td><td>10.1.1.2</td><td>eth1 (Ethernet 2nd adapter)</td><td>10</td></tr><tr><td>192.168.1.0</td><td>255.255.255.0</td><td>10.1.1.3</td><td>eth1 (Ethernet 2nd adapter)</td><td>10</td></tr></tbody></table> <p>Router2 </p> <table><tbody><tr><th>Network ID</th><th>Network mask</th><th>Gateway</th><th>Interface (examples; may vary)</th><th>Cost (decreases the <a href="/facts/Time_to_live/CMFdghQh">TTL</a>)</th></tr><tr><td>0.0.0.0 (default route)</td><td>0.0.0.0</td><td>10.1.1.1</td><td>eth0 (Ethernet 1st adapter)</td><td>10</td></tr><tr><td>172.16.1.0</td><td>255.255.255.0</td><td>172.16.1.1</td><td>eth1 (Ethernet 2nd adapter)</td><td>10</td></tr></tbody></table> <p>Router3 </p> <table><tbody><tr><th>Network ID</th><th>Network mask</th><th>Gateway</th><th>Interface (examples; may vary)</th><th>Cost (decreases the <a href="/facts/Time_to_live/CMFdghQh">TTL</a>)</th></tr><tr><td>0.0.0.0 (default route)</td><td>0.0.0.0</td><td>10.1.1.1</td><td>eth0 (Ethernet 1st adapter)</td><td>10</td></tr><tr><td>192.168.1.0</td><td>255.255.255.0</td><td>192.168.1.96</td><td>eth1 (Ethernet 2nd adapter)</td><td>10</td></tr></tbody></table> <p>Router2 manages its attached networks and default gateway; router 3 does the same; router 1 manages all routes within the internal networks. </p> Accessing internal resources If PC2 (172.16.1.100) needs to access PC3 (192.168.1.100), since PC2 has no route to 192.168.1.100 it will send packets for PC3 to its default gateway (router2). Router2 also has no route to PC3, and it will forward the packets to its default gateway (router1). Router1 has a route for this network (192.168.1.0/24) so router1 will forward the packets to router3, which will deliver the packets to PC3; reply packets will follow the reverse path back to PC2. Accessing external resources If any of the computers try to access a webpage on the Internet, like https://en.wikipedia.org/, the destination will first be resolved to an IP address by using <a href="/facts/Domain_Name_System/rfxdWFsj">DNS</a>-resolving. The IP-address could be 91.198.174.2. In this example, none of the internal routers know the route to that host, so they will forward the packet through router1's gateway or <a href="/facts/Default_route/qEc68cgL">default route</a>.<a class="footnote-ref" id="fnref:1" href="#fn:1"><sup>1</sup></a> Every router on the packet's way to the destination will check whether the packet's destination IP-address matches any known network routes. If a router finds a match, it will forward the packet through that route; if not, it will send the packet to its own default gateway. Each router encountered on the way will store the packet ID and where it came from so that it can pass the response packet back to the sender. The packet contains source and destination, not all router hops. At last the packet will arrive back to router1, which will check for matching packet ID and route it accordingly through router2 or router3 or directly to PC1 (which was connected in the same network segment as router1). The packet doesn't return If router1 routing table does not have any route to 192.168.1.0/24, and PC3 tries to access a resource outside its own network, then the outgoing routing will work until the reply is fed back to router1. Since the route is unknown to router1, it will go to router1's default gateway, and never reach router3. In the logs of the resource they will trace the request, but the requestor will never get any information. The packet will die because the <a href="/facts/Time_to_live/CMFdghQh">TTL</a>-value decreased to less than 1 when it was traveling through the routers, or the router will see that it has a private IP and discard it. This could be discovered by using the <a href="/facts/Microsoft_Windows/bwhAhuSL">Microsoft Windows</a> utility <a href="/facts/PathPing/vpL6IzPd">PathPing</a> or <a href="/facts/MTR_(software)/QNhGQ1KC">MTR</a> on Unix-like operating systems, since the ping will stop at the router which has no route or a wrong route. (Note that some routers will not reply to pinging). <h2 id="utilities">Utilities</h2> <p>Various <a href="/facts/Utility_software/Hn3XtISQ">utility software</a> can show the default gateway. On Windows, <a href="/facts/Ipconfig/JMxvdlgM">ipconfig</a> may be used,<a class="footnote-ref" id="fnref:2" href="#fn:2"><sup>2</sup></a> while on <a href="/facts/Unix/0pNL2seI">Unix</a> systems, <a href="/facts/Ifconfig/CwBoHjpf">ifconfig</a> or <a href="/facts/Netstat/h2lAhfA5">netstat</a> may be used.<a class="footnote-ref" id="fnref:3" href="#fn:3"><sup>3</sup></a> On Linux netstat has been superseded by <a href="/facts/Iproute2/JoyfcKU5">iproute2</a>.<a class="footnote-ref" id="fnref:4" href="#fn:4"><sup>4</sup></a><a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> </p> <h2 id="external-links">External links</h2> <ul><li><a href="http://tldp.org/LDP/nag/node27.html">The Linux Documentation Project</a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>Bhardwaj, Mukesh (2019-01-11). "192.168.1.1 Login Page, Username, Password, and WiFi Settings". iTech Hacks. Retrieved 2019-02-25. <a href="https://itechhacks.com/192-168-1-1-login-admin-password/" target="_blank">https://itechhacks.com/192-168-1-1-login-admin-password/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"Top 7 TCP/IP Utilities For Networking Pros". pluralsight.com. Retrieved 2019-05-05. <a href="https://www.pluralsight.com/blog/it-ops/top-7-tcpip-utilities-every-networking-pro-should-know" target="_blank">https://www.pluralsight.com/blog/it-ops/top-7-tcpip-utilities-every-networking-pro-should-know</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>Henry-Stocker, Sandra (2013-08-03). "Unix: Getting from here to there (routing basics)". Network World. Retrieved 2019-05-05. <a href="https://www.networkworld.com/article/2707620/unix---getting-from-here-to-there--routing-basics-.html" target="_blank">https://www.networkworld.com/article/2707620/unix---getting-from-here-to-there--routing-basics-.html</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"News: Deprecation of net-tools". archlinux.org. Retrieved 2020-05-18. <a href="https://www.archlinux.org/news/deprecation-of-net-tools/" target="_blank">https://www.archlinux.org/news/deprecation-of-net-tools/</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Deprecated Linux networking commands and their replacements". Doug Vitale Tech Blog. 2011-12-21. Retrieved 2020-05-18. <a href="https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/" target="_blank">https://dougvitale.wordpress.com/2011/12/21/deprecated-linux-networking-commands-and-their-replacements/</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> </ol>