Router vs Gateway – Why Routers Can’t Convert Different Network Models

iplayer3osiroutertcp

We know that Router can't be used for converting different model (e.g OSI model to TCP/IP or TCP/IP model to OSI) of network. It isn't a multiprotocol converter. But gateway is a highly sophisticated router which can be used for connecting different model of network. I have been finding actual reason behind this but failed to find any fruitful stuff. Can anybody help to make out above concepts.

Best Answer

Models are models - concepts for thought. Like philosophies - sometimes one fits better, some other time the other one.

Converting between TCP/IP model and OSI model doesn't make sense. It's like trying to convert a glass that's half full to a glass that's half empty. It's only a matter of perspective.

The OSI and TCP/IP models are actually very similar. OSI is more detailed (and more theoretical), and TCP/IP focuses on the network (OSI)/internet (IP) and the transport layer, naturally. OSI splits IP's application layer into application, presentation and session (not too common in real life), and IP's link layer is represented by OSI's data link and physical layers (very useful in practice).

On the network layer, router and gateway are the very same thing. There are various feature levels (concerning filtering, firewalling, inspection, address translation, ...) but both terms are interchangeable still.

Gateway can also refer to various other concepts that connect different realms. Gateways from different OSI layers (bridges, routers, proxies, application-layer gateways, ...) are generally different, but even gateways working in the same layer can be vastly different.

Higher-layer gateways can even be used to translate between protocols with a similar purpose, like an FTP-over-HTTP proxy. But all that is off-topic here for working above the transport layer.