Vol. I · No. 46The hardware sectionSat, 10 Oct 2026
Layer 3+ · Translation device

Gateway

the protocol gateway

A gateway joins two networks that don’t speak the same language. It receives traffic in one protocol, translates it end to end, and re-emits it in the other — the interpreter between dissimilar systems.

A gateway connects two different kinds of network and translates fully between their protocols.

Operates at
Layer 3 and up
often to L7
Joins
Unlike networks
different stacks
Does
Translation
protocol ↔ protocol
Example
IoT / VoIP
legacy bridges

How it works

Two protocols that can’t talk — until the gateway
Network A
protocol X
one stack
message in X
Gateway
translate
X ⇄ Y
message in Y
Network B
protocol Y
a different stack
Translate, don’t just forward
protocol X in→ fully decoded
protocol Y out ← re-encoded→ sent onward

A router forwards; a gateway translates. It fully decodes traffic in one protocol and re-encodes it in another, letting systems that share no common language interoperate.

The main points

What a gateway does, step by step

1
Receive in protocol X

Traffic arrives from the first network.

2
Decode the message

It parses the data all the way up the stack.

3
Re-encode in protocol Y

It rebuilds the message in the second network’s language.

4
Forward to network B

The translated message is sent on.

In cybersecurity

A gateway reads everything it translates, so it’s a natural inspection point — and a bridge that could join zones that shouldn’t meet.

Full inspection

It already parses the entire payload.

Translation errors

Mismatches can leak or corrupt data.

Zone bridging

It can wrongly connect different trust levels.

Legacy exposure

It often fronts old, unpatched systems.

A single interpreter

A bug here affects both sides at once.

Strict validation

Sanitise input on both protocols.

Protocols it runs

IPSIPMQTT

Sits beside

RouterFirewall

On the bench

Gateway — Protocol gateway