3Com Router 3031, Command Reference Manual

Page: 554 / 838

554 C
HAPTER
6: R
OUTING
P
ROTOCOL
rip authentication-mode Syntax
rip authentication-mode { { simple password } | { md5 { key-string key-string |
key-id key-id } } }
undo rip authentication-mode
View
Interface view
Parameter
■
simple: Simple text authentication mode.
■
password: Simple text authentication key, in character string format with 1 to
16 characters in simple text mode or 24 characters in cipher text mode.
■
md5: MD5 cipher text authentication mode.
■
key-string: MD5 cipher text authentication key, in character string format with
1 to 16 characters in simple text mode or 24 characters in cipher text mode.
■
key-id: MD5 cipher text authentication identifier, ranging from 1 to 255.
Description
Using the rip authentication-mode command, you can configure RIP-2
authentication mode and corresponding parameters. Using the undo rip
authentication-mode command, you can cancel the RIP-2 authentication.
RIP-1 does not support authentication. There are two RIP authentication modes:
simple text authentication and MD5 cipher text authentication. When MD5 cipher
text authentication mode is used, there are two types of packet formats. One of
them is described in RFC 1723, which was brought forward earlier. The other
format is the one described specially in RFC 2082. The router supports both of the
packet formats and the user can select either of them on demands.
For the related command, see rip version.
Example
Specify Interface serial1/0/0 to use the simple text authentication with the key as
aaa.
[3Com] interface serial1/0/0
[3Com-Serial1/0/0] rip version 2
[3Com-Serial1/0/0] rip authentication-mode simple aaa
rip authentication-mode Syntax
rip authentication-mode md5 type { usual | nonstandard }
View
Interface view
Parameter
■
usual: Specifies the MD5 cipher text authentication packet to use the general
packet format (RFC1723 standard format).
■
nonstandard: Specifies the MD5 cipher text authentication packet to use a
nonstandard packet format described in RFC2082.