UK The short answer
The gateway vs router question comes up because the two words overlap. A router is a specific device with a specific job: it moves IP packets from one network to another, choosing a path from its routing table. Both networks speak IP, and the router does not change what the packets contain.
A gateway is a broader idea. It is any node that acts as the way in and out of a network, and in the stricter sense one that joins networks or systems that use different protocols, translating between them. That translation can happen at any layer of the OSI model, up to the application layer, where a gateway reads data in one format and rewrites it in another.
So a router can be a gateway, and very often is, but plenty of gateways are not routers at all.
Three meanings of “gateway”
Most confusion comes from the same word being used for three different things:
-
//
The default gateway. In a computer’s network settings, the default gateway is the address it sends traffic to when the destination is outside its own subnet. On almost every network that address belongs to the local router, which is why the two terms are used interchangeably.
-
//
The home or ISP gateway. Broadband providers often call their box a gateway because it combines a modem, a router, a Wi-Fi access point and sometimes a phone adapter in one case. The routing part works like any other router.
-
//
The protocol gateway. A device that connects systems with different protocols, such as a VoIP gateway between phone lines and IP, a Modbus gateway between serial and Ethernet, or an IoT gateway between machines and the cloud. This is the meaning used in industrial networking.
Router vs gateway compared
The table compares a router with a protocol gateway, the meaning that matters most when choosing hardware.
| Feature | Router | Protocol gateway |
|---|---|---|
| Main job | Forward IP packets between networks | Translate data between different protocols |
| OSI layer | Layer 3 (network) | Any layer, often up to layer 7 |
| Protocols on each side | IP on both sides | Different, such as Modbus RTU and MQTT |
| Changes the data? | No, apart from headers and NAT | Yes, it reformats and often processes it |
| Key settings | Routes, NAT, firewall rules, VPN | Device addresses, register maps, topics, data formats |
| Typical hardware | Dedicated network appliance | Embedded computer running gateway software |
Our explainers on what a router does and on layer 3 switches vs routers go further into routing itself.
Industrial routers vs IoT gateways
On an industrial site the question usually becomes whether you need an industrial router or an IoT gateway. They can look alike, as both are small DIN-rail or wall-mounted boxes, often with 4G or 5G, but they solve different problems.
An industrial router connects a remote site or machine network to a wider network. It handles IP routing, NAT, firewall rules, VPN tunnels and cellular failover, so that engineers can reach PLCs and HMIs that already speak Ethernet.
An IoT gateway connects the equipment itself. Industrial IoT gateways have serial, CAN and digital I/O ports as well as Ethernet. They poll meters and controllers in their own protocols, turn the readings into named values, filter or analyse them locally and publish the results over MQTT, OPC UA or HTTPS. A Modbus gateway is a simpler version that only converts between Modbus RTU and Modbus TCP.
Many systems use both: the gateway collects and translates, and the router or firewall controls what leaves the site. An IoT gateway built on a general-purpose computer can also route traffic and run a VPN when the project only needs light routing, while a dedicated router remains the better choice for complex networks.
Worked example: a remote pumping station
A water company wants flow, pressure and pump status from an unmanned pumping station. The station has a PLC with a Modbus RTU serial port, two flow meters on RS-485 and a few digital signals from float switches and door contacts. None of these devices speaks IP.
An IoT gateway in the control cabinet polls the PLC and meters over RS-485 and reads the digital inputs directly. It converts the raw registers into named values such as pump1/flow, keeps a local log in case the link drops, and publishes the data over MQTT with TLS to the company’s broker. That is protocol translation, so it is gateway work.
The connection back to the control room runs over 4G. If the gateway has its own cellular module, it can send the data itself. If the site already has an industrial router, the gateway sends its traffic through it, and the router handles the VPN tunnel, firewall rules and cellular failover. That is routing work.
Engineers who need to reach the PLC’s programming port remotely use the router’s VPN. Dashboards and alarm systems use the gateway’s MQTT data, so they never need direct access to the PLC at all, which keeps the control network simpler to protect.
Quick answers on gateways and routers
Gateway vs router: common questions
Is a router a gateway?
Usually, yes. A router acts as the default gateway for the devices on its local network, but it does not translate between protocols.
Is a gateway a router?
Not necessarily. A protocol gateway may have no routing function at all and simply convert data from one system to another.
What is my default gateway?
The address your device sends off-network traffic to. On most networks it is the local router’s IP address, shown in the device’s network settings.
Is a modem a gateway?
On its own, no. A modem converts signals for the line; a broadband “gateway” is a modem combined with a router and Wi-Fi.
Do I need a gateway or a router for IIoT?
It depends on the devices. If your machines already speak Ethernet, a router may be enough; if they use serial, CAN or fieldbus, you need a gateway.
We supply our gateways with the operating system, wireless modules and network settings configured as part of the standard build.