Internetwork Packet Exchange (IPX) is the network-layer protocol in the IPX/SPX protocol suite. IPX is derived from Xerox Network Systems' IDP. It also has the ability to act as a transport layer protocol.
The IPX/SPX protocol suite was very popular through the late 1980s and mid-1990s because it was used by Novell NetWare, a network operating system. Due to Novell NetWare's popularity, IPX became a prominent protocol for internetworking.
A big advantage of IPX was a small memory footprint of the IPX driver, which was vital for DOS and Windows up to Windows 95 due to the limited size at that time of conventional memory. Another IPX advantage was easy configuration of its client computers. However, IPX does not scale well for large networks such as the Internet.[1] As such, IPX usage decreased as the boom of the Internet made TCP/IP nearly universal.
Computers and networks can run multiple network protocols, so almost all IPX sites also ran TCP/IP, to allow Internet connectivity.[2] It was also possible to run later Novell products without IPX, with the beginning of full support for both IPX and TCP/IP by NetWare version 5[3] in late 1998.
A big advantage of IPX protocol is its little or no need for configuration. In the time when protocols for dynamic host configuration did not exist and the BOOTP protocol for centralized assigning of addresses was not common, the IPX network could be configured almost automatically. A client computer uses the MAC address of its network card as the node address and learns what it needs to know about the network topology from the servers or routers – routes are propagated by Routing Information Protocol, services by Service Advertising Protocol.
A small IPX network administrator had to care only
Each IPX packet begins with a header with the following structure:
| Octets | Field | |
|---|---|---|
| 2 | Checksum (always 0xFFFF – no checksum) | |
| 2 | Packet Length (including the IPX header) | |
| 1 | Transport Control (hop count) | |
| 1 | Packet Type | |
| 12 | Destination address | |
| 12 | Source address |
The Packet Type values are:
| Value | Meaning/Protocol | |
|---|---|---|
| 0 | Unknown | |
| 1 | RIP (Routing Information Protocol) (RFC 1582, RFC 2091) | |
| 2 | Echo Packet | |
| 3 | Error Packet | |
| 4 | PEP (Packet Exchange Protocol), used for SAP (Service Advertising Protocol) | |
| 5 | SPX (Sequenced Packet Exchange) | |
| 17 | NCP (NetWare Core Protocol) | |
| 20 | Broadcast[4] |
An IPX address has the following structure:
| Octets | Field | |
|---|---|---|
| 4 | Network number | |
| 6 | Node number | |
| 2 | Socket number |
The network number allows to address (and communicate with) the IPX nodes which do not belong to the same network or cabling system. The cabling system is a network in which a data link layer protocol can be used for communication. To allow communication between different networks, they must be connected with IPX routers. A set of interconnected networks is called an internetwork. Any Novell NetWare server may serve as an IPX router. Novell also supplied stand-alone routers. Multiprotocol routers of other vendors often support IPX routing. Using different frame formats in one cabling system is possible, but it works similarly as if separate cabling systems were used (i.e. different network numbers must be used for different frame formats even in the same cabling system and a router must be used to allow communication between nodes using different frame formats in the same cabling system).
The node number is used to address an individual computer (or more exactly, a network interface) in the network. Client stations use its network interface card MAC address as the node number.
The value FF:FF:FF:FF:FF:FF may be used as a node number in a destination address to broadcast a packet to "all nodes in the current network".
The socket number serves to select a process or application in the destination node.The presence of a socket number in the IPX address allows the IPX to act as a transport layer protocol, comparable with the User Datagram Protocol (UDP) in the Internet protocol suite.
| Socket number | Protocol | |
|---|---|---|
| 0x0001–0x0BB8 | Registered by Xerox | |
| 0x0001 | Routing Information Packet | |
| 0x0002 | Echo Protocol Packet | |
| 0x0003 | Error Handling Packet | |
| 0x0020–0x003F | Experimental | |
| 0x0BB9–0xFFFF | Dynamically Assigned | |
| 0x0451 | NetWare Core Protocol (NCP – used by Novell NetWare servers) | |
| 0x0452 | Service Advertising Protocol (SAP) | |
| 0x0453 | Routing Information Protocol (RIP) | |
| 0x0455 | NetBIOS | |
| 0x0456 | Diagnostic Packet | |
| 0x0457 | Serialization Packet (used for NCP as well) | |
| 0x4000–0x4FFF | Dynamically Assigned Socket Numbers | |
| 0x4003 | Used by Novell NetWare Client | |
| 0x8000–0xFFFF | Statically Assigned Socket Numbers | |
| 0x8060 | LLC | |
| 0x9091 | TCP over IPXF | |
| 0x9092 | UDP over IPXF | |
| 0x9093 | IPXF, IPX Fragmentation Protocol |
The IPX network number is conceptually identical to the network part of the IP address (the parts with netmask bits set to 1); the node number has the same meaning as the bits of IP address with netmask bits set to 0. The difference is that the boundary between network and node part of address in IP is variable, while in IPX it is fixed. As the node address is usually identical to the MAC address of the network adapter, the Address Resolution Protocol is not needed in IPX.
For routing, the entries in the IPX routing table are similar to IP routing tables; routing is done by network address, and for each network address a network:node of the next router is specified in a similar fashion an IP address/netmask is specified in IP routing tables.
There are three routing protocols available for IPX networks. In early IPX networks, a version of Routing Information Protocol (RIP) was the only available protocol to exchange routing information. Unlike RIP for IP, it uses delay time as the main metric, retaining the hop count as a secondary metric. Since NetWare 3, the NetWare Link Services Protocol (NLSP) based on IS-IS is available, which is more suitable for larger networks. Cisco routers implement an IPX version of EIGRP protocol as well.[5]
IPX can be transmitted over Ethernet using one of the following 4 frame formats or encapsulation types:
In non-Ethernet networks only 802.2 and SNAP frame types are available.