Movatterモバイル変換


[0]ホーム

URL:


Jump to content
WikipediaThe Free Encyclopedia
Search

Internetwork Packet Exchange

From Wikipedia, the free encyclopedia
(Redirected fromIPX)
Network protocol
"IPX" redirects here. For other uses, seeIPX (disambiguation).
This article has multiple issues. Please helpimprove it or discuss these issues on thetalk page.(Learn how and when to remove these messages)
This articlemay be too technical for most readers to understand. Pleasehelp improve it tomake it understandable to non-experts, without removing the technical details.(July 2019) (Learn how and when to remove this message)
This articleneeds additional citations forverification. Please helpimprove this article byadding citations to reliable sources. Unsourced material may be challenged and removed.
Find sources: "Internetwork Packet Exchange" – news ·newspapers ·books ·scholar ·JSTOR
(July 2019) (Learn how and when to remove this message)
(Learn how and when to remove this message)

Internetwork Packet Exchange (IPX) is thenetwork-layer protocol in theIPX/SPXprotocol suite. IPX is derived fromXerox Network Systems'IDP. It also has the ability to act as atransport layer protocol.

The IPX/SPX protocol suite was very popular through the late 1980s and mid-1990s because it was used byNovellNetWare, anetwork operating system. Due to Novell NetWare's popularity, IPX became a prominent protocol forinternetworking.

A big advantage of IPX was a smallmemory footprint of the IPX driver, which was vital forDOS andWindows up toWindows 95 due to the limited size at that time ofconventional 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 theInternet madeTCP/IP nearly universal.

Computers and networks can run multiplenetwork 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.

Description

[edit]

A big advantage of IPX protocol is its little or no need for configuration. In the time when protocols fordynamic host configuration did not exist and theBOOTP protocol for centralized assigning of addresses was not common, the IPX network could be configured almost automatically. A client computer uses theMAC address of its network card as the node address and learns what it needs to know about the network topology from the servers orrouters – routes are propagated byRouting Information Protocol, services byService 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 (NovellNetWare 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 packet structure

[edit]

Each IPX packet begins with a header with the following structure:

OctetsField
2Checksum (always 0xFFFF – no checksum)
2Packet Length (including the IPX header)
1Transport Control (hop count)
1Packet Type
12Destination address
12Source address

The Packet Type values are:

ValueMeaning/Protocol
0Unknown
1RIP (Routing Information Protocol) (RFC 1582, RFC 2091)
2Echo Packet
3Error Packet
4PEP (Packet Exchange Protocol), used for SAP (Service Advertising Protocol)
5SPX (Sequenced Packet Exchange)
17NCP (NetWare Core Protocol)
20Broadcast[4]

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 network orcabling system. Thecabling system is a network in which adata link layer protocol can be used for communication. To allow communication between different networks, they must be connected with IPXrouters. A set of interconnected networks is called aninternetwork. AnyNovell NetWare server may serve as an IPX router. Novell also supplied stand-alone routers. Other vendors ' multiprotocol routers often support IPX routing. Using differentframe 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).

  • Logical networks are assigned a unique 32-bit address in the range 0x1 to 0xFFFFFFFE (hexadecimal).
  • Hosts have a 48-bit node address, which is by default set to the 6 bytes of the network interface cardMAC address. Network addresses, which exist in addition to the node address but are not part of the MAC layer, are assigned only if an IPX router is present or by manual configuration in the network. The network address covers every network participant that can talk to another participant without the aid of an IPX router. In combination, both network and node address form an 80-bit unique identifier for each IPX node across connected logical networks. The node number itself is unique to the logical network only.
  • 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. Client stations use its network interface cardMAC address as the node number.

The value FF:FF:FF:FF:FF:FF may be used as a node number in a destination address tobroadcast a packet to "all nodes in the current network".

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 atransport layer protocol, comparable with theUser Datagram Protocol (UDP) in theInternet protocol suite.

Socket numberProtocol
0x0001–0x0BB8Registered byXerox
0x0001Routing Information Packet
0x0002Echo Protocol Packet
0x0003Error Handling Packet
0x0020–0x003FExperimental
0x0BB9–0xFFFFDynamically Assigned
0x0451NetWare Core Protocol (NCP – used byNovell NetWare servers)
0x0452Service Advertising Protocol (SAP)
0x0453Routing Information Protocol (RIP)
0x0455NetBIOS
0x0456Diagnostic Packet
0x0457Serialization Packet (used for NCP as well)
0x4000–0x4FFFDynamically Assigned Socket Numbers
0x4003Used byNovell NetWare Client
0x8000–0xFFFFStatically Assigned Socket Numbers
0x8060LLC[4]
0x9091TCP over IPXF
0x9092UDP over IPXF
0x9093IPXF, IPX Fragmentation Protocol

Comparison with IP

[edit]

The IPX network number is conceptually identical to the network part of theIP address (the parts withnetmask 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, theAddress Resolution Protocol is not needed in IPX.

Forrouting, the entries in the IPXrouting 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 ofRouting Information Protocol (RIP) was the only available protocol to exchange routing information. Unlike RIP forIP, it uses delay time as the main metric, retaining the hop count as a secondary metric. Since NetWare 3, theNetWare Link Services Protocol (NLSP) based onIS-IS is available, which is more suitable for larger networks.Cisco routers implement an IPX version ofEIGRP protocol as well.[5]

Frame formats

[edit]

IPX can be transmitted over Ethernet using one of the following 4 frame formats or encapsulation types:

  • 802.3 (raw) encapsulation comprises an IEEE 802.3 frame header (destination MAC, source MAC, length) immediately followed by IPX data. It is used in legacy systems, and can be distinguished by the first two bytes of the IPX header always containing a value of 0xFFFF, which cannot be interpreted as valid LLC Destination and SourceService Access Points in this location of the frame.
  • 802.2 (LLC or Novell) comprises an IEEE 802.3 frame header (destination MAC, source MAC, length) followed by anLLC header (DSAP 0xE0,SSAP 0xE0, control 0x03) followed by IPX data. The 0xE0 fields of the LLC header indicate "NetWare".
  • 802.2 (SNAP) comprises an IEEE 802.3 frame header, an LLC header (DSAP 0xAA, SSAP 0xAA, control 0x03), a SNAP header (OUI 0x000000, type 0x8137), and IPX data. The 0xAA fields of the LLC header indicate "SNAP", and the OUI 0x000000 in the SNAP header indicates an encapsulatedEtherType.
  • Ethernet II encapsulation comprises an Ethernet II frame header (destination MAC, source MAC,EtherType 0x8137) followed by IPX data.

In non-Ethernet networks, only 802.2 and SNAP frame types are available.

References

[edit]
  1. ^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.
  2. ^"Do you still support IPX/SPX on your Windows servers?".TechRepublic. February 12, 2001. Archived fromthe original on July 10, 2012.
  3. ^Maintaining IPX Compatibility During a Migration to TCP/IP on a NetWare Network. support.novell.com.
  4. ^ab"A Standard for the Transmission of 802.2 Packets over IPX Networks". IETF.
  5. ^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.

External links

[edit]
Retrieved from "https://en.wikipedia.org/w/index.php?title=Internetwork_Packet_Exchange&oldid=1279438020"
Categories:
Hidden categories:

[8]ページ先頭

©2009-2025 Movatter.jp