3com 3031 Instruccion De Instalación
482
C
HAPTER
39: RIP C
ONFIGURATION
configurations on all routers that run RIP to avoid adding unnecessary network
traffic or causing network route oscillation.
traffic or causing network route oscillation.
Configuring Zero Field
Check of an Interface
Packet
As RFC1058 provides, some fields in a RIP-1 packet must be 0, and they are called
zero fields. Therefore, when an interface version is set as RIP-1, the zero field
check should be performed on the packet. But if the value in the zero filed is not
zero, processing will be refused. As there are no zero fields in an RIP-2 packet, this
configuration is invalid for RIP-2.
zero fields. Therefore, when an interface version is set as RIP-1, the zero field
check should be performed on the packet. But if the value in the zero filed is not
zero, processing will be refused. As there are no zero fields in an RIP-2 packet, this
configuration is invalid for RIP-2.
Perform the following in the RIP View.
By default, zero field check is enabled on RIP-1 packets.
Specifying RIP Version of
an Interface
RIP has two versions, RIP-1 and RIP-2. You can specify the version of the RIP packet
processed by an interface.
processed by an interface.
RIP-1 broadcasts the packets. RIP-2 can transmit packets by both broadcast and
multicast. By default, multicast is adopted for packets transmission. In RIP-2, the
multicast address is 224.0.0.9. The advantage of multicast packet transmission is
that it prevents RIP-disabled hosts from receiving RIP broadcast packets. In
addition, it also helps RIP-1-enabled hosts to avoid mistakenly receiving and
processing routes with subnet masks of RIP-2. When RIP-2 is enabled on an
interface, RIP-1 packets can also be received.
multicast. By default, multicast is adopted for packets transmission. In RIP-2, the
multicast address is 224.0.0.9. The advantage of multicast packet transmission is
that it prevents RIP-disabled hosts from receiving RIP broadcast packets. In
addition, it also helps RIP-1-enabled hosts to avoid mistakenly receiving and
processing routes with subnet masks of RIP-2. When RIP-2 is enabled on an
interface, RIP-1 packets can also be received.
Perform the following configuration in interface view.
By default, the interface receives and sends RIP-1 packets. When the interface RIP
version is set to RIP-2, the interface will transmit packets in multicast mode.
version is set to RIP-2, the interface will transmit packets in multicast mode.
Configuring RIP Packet
Authentication
RIP-1 does not support packet authentication. But when the interface operates
RIP-2, the packet authentication can be configured.
RIP-2, the packet authentication can be configured.
RIP-2 supports two authentication modes, plain text authentication and MD5
authentication. MD5 authentication uses two packet formats: One follows
RFC1723 (RIP Version 2 Carrying Additional Information) and the other follows the
RFC2082 (RIP-2 MD5 Authentication).
authentication. MD5 authentication uses two packet formats: One follows
RFC1723 (RIP Version 2 Carrying Additional Information) and the other follows the
RFC2082 (RIP-2 MD5 Authentication).
Table 554 Configuring zero field check of an interface packet
Operation
Command
Configure zero field check on the RIP-1 packet
checkzero
Disable zero field check on the RIP-1 packet
undo checkzero
Table 555 Specifying RIP version of an interface
Operation
Command
Specify the interface version as RIP-1
rip version 1
Specify the interface version as RIP-2
rip version 2 [ broadcast | multicast ]
Restore the default operating RIP
version on an interface
version on an interface
undo rip version { 1 | 2 }