Is a Gateway always a real computer or just a "logic" entity, which can be on any address, except the broadcast IP?

  • 9
    The modern and arguably more correct term for a gateway is router. Routers can exist purely in software, conventional computers such as PC's, laptops and server systems can be used as routers but generally dedicated hardware devices are used
    – HBruijn
    Commented Jan 29, 2019 at 8:11
  • 2
    What do you mean by "logic entity"?
    – Barmar
    Commented Jan 29, 2019 at 17:50
  • 2
    @HBruijn, in most cases a gateway is a router. The general term is that a gateway is the host on the network to which other hosts send traffic that it destined for a different network. That doesn't mean that is must be a router. It could be a proxy, ALG, etc. Also, there may be a corner case where any traffic destined for a different network needs to be trapped and not forwarded by the gateway, in which case it is not a router because it is not routing packets between networks.
    – Ron Maupin
    Commented Jan 29, 2019 at 18:58
  • I'd wager that a system that is capable of making forwarding decisions based on destination ip addresses does not have to be Turing complete ... so, no, a router need not be a computer (same applies one level below for bridges and one level high for gateways, though possible to different extents. Nevertheless, each such system is typically a device (or collection of devices) that can be configured administratively or by additional applications (such as routing protocols) - and to even be able to process a configuration, these things tend to be (specialized) computers. Commented Jan 29, 2019 at 21:45
  • @Barmar I mean if a Gateway must be a specialized hardware device like a Bridge or Router, or if it could be just a piece of information like a setting in a server, which is kind of mutable, if you think in terms of programming languages.
    – Semo
    Commented Jan 30, 2019 at 5:38

4 Answers 4


Default route (aka gateway address) has to be owned by something that is capable of forwarding packets to the rest of the internet, and which is willing to do so. It doesn't have to be the "principal" IP address of the thing that owns it (whatever that means). It can be a logical address that floats between two or more devices, and in high-availability setups it often is.

The only requirement, in order that routing works, is that whatever device currently owns and advertises the address, that device can and will route traffic.

  • 6
    ... Or at least pretend to. Commented Jan 29, 2019 at 9:57
  • 2
    @Shadur I'm interested in how routing can work if default route only pretends to actually, y'know, route traffic.
    – MadHatter
    Commented Jan 29, 2019 at 10:06
  • 1
    Routing itself won't work, but if all you want to allow is browsing you could have the "gateway" intercept and run a transparent proxy on ports 53, 80 and 443, and keep the system itself as isolated as possible. Commented Jan 29, 2019 at 10:09
  • 7
    OK. I don't disagree, but that's not routing. I stand by my assertion that in order for routing to work, the router must actually route, and it sounds like you wouldn't disagree with that.
    – MadHatter
    Commented Jan 29, 2019 at 10:31
  • 1
    Fair point, but "gateway" as it's used in this question is default route, ie next-hop-of-last-resort. That has to be able to get you not only to any internal subnets that you don't have specific routes for, but to everything else as well.
    – MadHatter
    Commented Jan 29, 2019 at 20:36

The IP address of the gateway can be any valid host IP address in the subnet, i.e. not the network address itself nor the broadcast address. This IP address does not need to belong to a single computer or router, it can be a "floating" IP address used by several gateways. Check out the Wikipedia articles on HSRP, VRRP, GLBP, or CARP.

For example, when the subnet is, then:

  • the network address is,
  • the broadcast address is, and
  • the range of valid host addresses is from till, inclusive.

The gateway must be any of these valid host addresses, e.g. The settings of your computer would then be, e.g.:

  • IP address:
  • Subnet mask:
  • Default gateway:

Now adding in one of the first-hop redundancy protocols, the actual gateways (routers) can have the IP address and but use the virtual IP address of to present themselves as the default gateway to the subnet.


"Logical entity" in your usage is a tiny bit confusing. But I'll try to answer it best I can.

From my experience, a gateway in an IP configuration is usually a physical device. While it doesn't have to be a computer in the traditional sense (it can also be a network appliance) it does have to be device.

As you may know, the purpose that a default gateway serves is to act as a forwarding entity for all requests that a.) the computer doesn't already have in its routing table or has an entry instructing the system to forward the request to an IP that happens to be the gateway and/or b.) that are outside of the broadcast domain. The default gateway is never used in situations where two hosts are on the same broadcast domain (i.e. a network topology created by a switch) because the system can use the subnet's broadcast address to find the MAC address of a system owning a particular IP address.

In short, to answer your question, technically, you can set your default gateway as any IP address on a connected network. Windows or most other OSs for that matter won't stop you because they often don't perform verification of TCP/IP details. If you're setting it, you're most likely technically-savvy enough to understand the distinction. However, if it is the IP address of a device that is unable to forward, then it will result in errors in applications reliant on routing (i.e. a web browser) because the device won't be prepared with a routing table or a routing service to forward the request.

Someone much more experienced than myself, however, should be able to easily correct me if I am wrong.

TL;DR - A physical device, most likely.

  • You can have multiple different IP subnets on the same broadcast domain. In such cases traffic between those hosts will flow via their default gateways unless extra entries are added to the hosts routing tables or ICMP redirects are in use. Commented Jan 29, 2019 at 16:29
  • @PeterGreen Yea, there are a lot of odd edge cases. For example, say and are on the same physical Ethernet LAN with the gateway for both being the same physical router at and respectively. If pings the first round-trip will be relayed through the gateway. The gateway may also send ICMP redirects to each host telling them they're on the same LAN. If so, each host will then then send ARP requests to get their peer's MAC addresses and all further communication will then occur directly between the peers (not via the gateway). Commented Jan 30, 2019 at 14:30
  • Note that with the above example, hosts need to be prodded (via an ICMP redirect) to broadcast an ARP request for the MAC address of a peer on a foreign network. Absent a redirect hosts won't make foreign-network ARP requests. Commented Jan 30, 2019 at 14:44

Routing table entries resolve a subnet to either a gateway or a network adapter.

A typical routing table for a device on a private network might, if you leave out the unnecessary stuff, look like via dev eth0

The most specific route wins for each destination, so the subnet route takes precedence over the default route for addresses in the subnet.

The gateway address is, in turn, resolved through the routing table, which determines the network interface it is given to as well as addressing on the lower layer.

So, for a packet to, the destination is looked up in the routing table, returning the default route, which has a gateway. The gateway is looked up again, returning the Ethernet interface.

Ethernet has MAC addresses, so an ARP lookup is done for the gateway address, and the MAC address for the gateway is used for the outgoing packet (which still uses the proper destination address in its IP header).

Other lower-level transports work differently, for example PPP links have a "peer address", so their device route uses a netmask of /32, and they skip ARP resolution and just send packets as "broadcast" over the PPP link.

Some IP stacks require manual creation of the device route, which makes this a bit more obvious:

ifconfig eth0 netmask broadcast up
route add -net netmask dev eth0
route add default via

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .