User`s guide

179
Plain password:
When set to “Plain password (V1+V2)”, the interface will use the first valid key it finds
(set on the Configuration – Network > IP Routing / Forwarding > RIP > Global
RIP settings > Authentication Keys > Authentication Key n pages), and use the
plaintext RIP authentication method before sending the packet out. If no valid key can be
found, the interface will not send any RIP packets. When receiving a RIP packet, a valid
plaintext key must be present in the packet before it will be accepted. This method can
be used with both RIP v1 and RIP v2.
MD5:
When set to “MD5 (V2 only)”, the interface will use the first valid key it finds (set on the
Configuration – Network > IP Routing / Forwarding > RIP > Global RIP settings
> Authentication Keys > Authentication Key n pages), and use the MD5
authentication algorithm before sending the packet out. If no valid key can be found, the
interface will not send any RIP packets. Received RIP packets must be authenticated
using the MD5 authentication algorithm before they will be accepted. This method can be
used with RIP v2.
Only send RIP advertisements when this interface is in service:
Select this parameter for RIP advertisements only to be sent when the interface is in the UP
state in the routing table.
Use Triggered RIP on this interface:
Enable triggered RIP (RFC2091). When triggered RIP is enabled, RIP timers are disabled.
Include this interface in Rip advertisements:
Select to cause the subnet configured on this interface to not be advertised by RIP.
Related CLI Commands
Entity
Instance
Parameter
Values
Equivalent Web Parameter
tun n rip 0,1
Enable RIP = 1
Disable RIP = 0
tun n ripip
Valid IP address
a.b.c.d
Unicast RIP update address
tun n ripauth 0-3
0 = None
1 = Access List
2 = Plain Password
3 = MD5 v2 only
tun n ripis on,off
Turn on to send updates only
when in service
tun n inrip on,off
Include interface subnet in RIP
advertisements
tun n triggeredrip on,off Enable RIP RFC2091