Introduction to Novell IPX
417
Routing Information Protocol
RIP information is exchanged between servers much the same way that SAP
information is. Servers build routing tables that contain entries for the net-
works they're directly connected to, they then broadcast this information to
all IPX-enabled interfaces.
Other servers on those segments receive those updates and broadcast their
RIP tables on their IPX interfaces. Just as SAP information travels from
server to server until all servers are enlightened, RIP information is spread
until all servers and routers know of the internetwork's routes. Like SAP
information, RIP information is broadcast at 60-second intervals. Let's take
a look at an IPX RIP packet with the Etherpeek analyzer.
Flags: 0x80 802.3
Status: 0x00
Packet Length:94
Timestamp: 15:23:05.642000 06/28/1998
802.3 Header
Destination: ff:ff:ff:ff:ff:ff Ethernet Brdcast
Source: 00:00:0c:8d:5c:9d
LLC Length: 76
802.2 Logical Link Control (LLC) Header
Dest. SAP: 0xe0 NetWare
Source SAP: 0xe0 NetWare Null LSAP
Command: 0x03 Unnumbered Information
IPX - NetWare Protocol
Checksum: 0xffff
Length: 72
Transport Control:
Reserved: %0000
Hop Count: %0000
Packet Type: 1 RIP
Destination Network: 0x00002300
Destination Node: ff:ff:ff:ff:ff:ff Ethernet
Brdcast
Destination Socket: 0x0453 Routing Information
Protocol
Source Network: 0x00002300
Copyright ©2002 SYBEX, Inc., Alameda, CA
www.sybex.com