tables. R1 shows a route to network 10.0.0.0 with an *, meaning that it is a candidate to be the
default route. In R3, 0.0.0.0 shows up in the routing table as the candidate default route. The
reason that R3 shows this information differently is that RIP advertises default routes using
network number 0.0.0.0. If IGRP or EIGRP were in use, there would be no route to 0.0.0.0 on
R3, and network 10.0.0.0 would be the candidate default route. That's because IGRP and
EIGRP would flag 10.0.0.0 as a candidate default route in their routing updates rather than
advertise the special case of 0.0.0.0.
network because ip classless is still configured. The trace commands in Example 5-17, which
show destinations in three different networks, all succeed. The trace commands each show that
the first router in the route was R1, then Dist1, and then the command finished. If n many other
routers had been present in the network of Figure 5-31, then these routers could have shown up
in the trace output as well. (In each case, the destination address was the address of some
loopback interface in Dist1, so there were no routers beyond Dist1.) ip classless was still
configured; it is recommended to configure ip classless if using any form of default routes.
Novell NetWare. Novell's NetWare protocol stack defines Internetwork Packet Exchange (IPX)
as a network layer equivalent protocol, as seen in Figure 5-32. IPX will be the focus of this
initial section.
part. As with IP and AppleTalk, all interfaces attached to the same data link use addresses in the
same network. Table 5-30 lists four features of IPX addressing. The features listed in Table
5-30 are the same features used to generically describe a well-designed Layer 3 addressing
scheme in Chapter 3, "OSI Reference Model & Layered Communication."
2 168.13.1.101 48 msec 56 msec 52 msec
R3#trace 1.1.222.2
Tracing the route to 1.1.222.2
2 168.13.1.101 48 msec 56 msec 52 msec
R3#