3com 8807 사용자 가이드
Configuring RIP
299
Specifying the
Operating State of the
Interface
In interface view, you can specify the operating state of RIP on the interface. For
example, whether RIP operates on the interface, namely, whether RIP update
packets are sent and received on the interface. In addition, whether an interface
sends or receives RIP update packets can be specified separately.
example, whether RIP operates on the interface, namely, whether RIP update
packets are sent and received on the interface. In addition, whether an interface
sends or receives RIP update packets can be specified separately.
Perform the following configuration in interface view.
The undo rip work command and the undo network command have similar but
not all the same functions. Neither of the two commands configures an interface
to receive or send RIP route. The difference also exists. RIP still advertises the routes
of the interface applying the undo rip work command. However, other interfaces
will not forward the routes of the interface applying the undo network
command. It seems that the interface is removed.
not all the same functions. Neither of the two commands configures an interface
to receive or send RIP route. The difference also exists. RIP still advertises the routes
of the interface applying the undo rip work command. However, other interfaces
will not forward the routes of the interface applying the undo network
command. It seems that the interface is removed.
In addition, rip work is functionally equivalent to both rip input and rip output
commands.
commands.
By default, all interfaces except loopback interfaces both receive and transmit RIP
update packets.
update packets.
Setting RIP-2 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: Simple authentication and MD5
authentication. MD5 authentication uses two packet formats: One follows
RFC1723 and the other follows the RFC2082.
authentication. MD5 authentication uses two packet formats: One follows
RFC1723 and the other follows the RFC2082.
The simple authentication does not ensure security. The authentication key not
encrypted is sent together with the packet, so the simple authentication cannot be
applied to the case with high security requirements.
encrypted is sent together with the packet, so the simple authentication cannot be
applied to the case with high security requirements.
Perform the following configuration in Interface view:
Table 267 Specify the operating state of the interface
Operation
Command
Enable the interface to run RIP
rip work
Disable the interface to run RIP
undo rip work
Enable the interface to receive RIP update packet
rip input
Disable the interface to receive RIP update packet
undo rip input
Enable the interface to send RIP update packet
rip output
Disable the interface to send RIP update packet
undo rip output
Table 268 Set RIP-2 packet authentication
Operation
Command
Configure RIP-2 simple authentication key
rip authentication-mode simple
password-string
password-string
Perform usual MD5 authentication on RIP-2
packets
packets
rip authentication-mode md5 usual
key-string
key-string
Perform nonstandard-compatible MD5
authentication on RIP-2 packets
authentication on RIP-2 packets
rip authentication-mode md5
nonstandard key-string key-id
nonstandard key-string key-id