Routed Protocols
Introduction
We all understand that TCP/IP, IPX-SPX are protocols which are used in a Local Area Network (LAN) so computers can communicate between with each other and with other computers on the Internet.
Chances are that in your LAN you are most probably running TCP/IP. This protocol is what we call a "routed" protocol. The term "routed" refers to something which can be passed on from one place (network) to another. In the example of TCP/IP, this is when you construct a data packet and send it across to another computer on the Internet
This ability to use TCP/IP to send data across networks and the Internet is the main reason it's so popular and dominant. If you're thinking also of NetBeui and IPx/SPX, then note that NetBeui is not a routed protocol, but IPX/SPX is! The reason for this is actually in the information a packet holds when it uses one of the protocols.
Let me explain:
If you looked at a TCP/IP or IPX/SPX packet, you will notice that they both contain a "network" layer. For TCP/IP, this translates to the IP layer (Layer 3), as for IPX/SPX, it's the IPX layer (Layer 3). To make it easy to understand, I will use TCP/IP as an example.
In the picture below, you can see a TCP/IP packet within an Ethernet II Frame (The frame is like an "envelope" which encapsulates the TCP/IP packet):
IPX/SPX contains a similar field which gives it the same ability, which is to send packets over to different networks.
NetBeui on the other hand has no such information! This means that NetBeui has no information about the destination network to which it needs to send the data, as it was developed for LAN use only, or you could say that all hosts are considered to be on the same logical network and all resources are considered to be local. This classifies NetBeui as a "non routed" protocol.
