1-14
For a message received, RIP compares the source IP address of the message with the IP address of
the interface. If they are not in the same network segment, RIP discards the message.
Follow these steps to enable source IP address check on incoming RIP updates:
To do…
Use the command…
Remarks
Enter system view
system-view
––
Enter RIP view
rip
[
process-id
] [
vpn-instance
vpn-instance-name
]
––
Enable source IP address
check on incoming RIP
messages
validate-source-address
Optional
Enabled by default
The source IP address check feature should be disabled if the RIP neighbor is not directly connected.
Configuring RIPv2 Message Authentication
In a network requiring high security, you can configure this task to implement RIPv2 message validity
check and authentication.
RIPv2 supports two authentication modes: plain text and MD5.
In plain text authentication, the authentication information is sent with the RIP message, which however
cannot meet high security needs.
Follow these steps to configure RIPv2 message authentication:
To do…
Use the command…
Remarks
Enter system view
system-view
––
Enter interface view
interface
interface-type interface-number
––
Configure RIPv2
authentication
rip authentication-mode
{
md5
{
rfc2082
key-string key-id
|
rfc2453 key-string
} |
simple
password
}
Required
This task does not apply to RIPv1 because RIPv1 does not support authentication. Although you can
specify authentication modes for RIPv1 in interface view, the configuration does not take effect.
Specifying a RIP Neighbor
Usually, RIP sends messages to broadcast or multicast addresses. On non broadcast or multicast links,
you need to manually specify RIP neighbors. If a specified neighbor is not directly connected, you must
disable source address check on incoming updates.
