RIP Interface Configuration¶
In basic configurations, RIP will automatically determine which interfaces to use. However, the interface behavior can be tuned when necessary.
To configure settings for RIP interfaces, start in
config-frr-rip mode and
interface <if-name> command to enter
tnsr(config)# route dynamic rip tnsr(config-frr-rip)# interface <if-name> tnsr(config-rip-if)#
config-rip-if mode contains the following commands:
- authentication mode <mode> [auth-length <type>]
Configures RIPv2 authentication for this interface. When authentication is enabled, TNSR will ignore updates from unauthenticated peers, including RIPv1 peers.
Updates from unauthenticated peers are ignored, but requests for routes from unauthenticated peers are still honored.
- mode <mode>
Selects the authentication mode.
MD5-based HMAC authentication, which is more secure than plain text. Keys for MD5 authentication are configured with the
config-ripmode (RIP Keychain Configuration).
Insecure plain text password authentication. The password is set with the
authentication stringcommand in this mode.
- auth-length <type>
Configures the expected length of the authentication data.
RFC-compatible data length (
20bytes), compatible only with older
- authentication key-chain <name>
The name of a key-chain to use with MD5 authentication (RIP Keychain Configuration).
- authentication string <auth-string>
The string used for plain text authentication. Must be less than 16 characters.
- receive version (1|2|both)
Configures the RIP versions allowed to be received by TNSR on this interface.
- send version (1|2|both)
Configures the RIP versions TNSR will transmit on this interface.
- split-horizon [poisoned-reverse]
Prevents a route from being advertised back to the interface through which it was received. This technique helps to prevent routing loops.
Instead of preventing such routes from being advertised, this option causes RIP to actively advertise the networks as unreachable by setting the metric to
16. This is more proactive for preventing routing loops, but the primary drawback is that this does not scale well, due to the size increase of advertisements.
When set, TNSR will transmit RIPv2 updates using broadcast on this interface instead of using multicast.