| Note: | This feature is supported only in the IPv4 operating mode. |
You can set the type of RIPv2 authentication for a specified device and line using the TCPIP RIP RIPAUTHENTICATION command. You can also use this command to inquire on the current authentication types set for each device and line configured on the system.
Issue the command as follows:
NW TCPIP RIP RIPAUTHENTICATION NP <np id> LINE <line id> <authentication type>
When you enter this command, the authentication type specified becomes the current authentication type.
Variables
The <np id> and <line id> variables are the network processor (device) ID and the Line ID respectively.
The Authentication Type option allows you to set a level of authentication for RIPv2 message processing. If the specified device and line are present, the authentication type is set to the value supplied. There are four authentication types supported by this command.
|
Authentication Type |
Description |
|---|---|
|
Ignore Authentication |
All RIP messages are processed, regardless of the presence or lack of the authentication fields in the RIP message. This setting is used primarily so that systems can process all incoming RIP information received. |
|
No Authentication |
Only those RIP messages that have the authentication field of the RIP message set to "NoAuthentication" are processed. RIP messages with no authentication field set or with a type other than "NoAuthentication" are ignored. |
|
Password |
Only those RIP messages that have the authentication field of the RIP message set to "Password" and have a supplied password that matches one defined in the current configuration are processed. RIP messages with no authentication field set, with a type other than "Password", or supply an invalid password are ignored. |
|
MD5 |
Only those RIP messages that have the authentication field of the RIP message set to "MD5" and have a supplied keychain that matches one defined in the current configuration are processed. RIP messages with no authentication field set, with a type other than "MD5" or that supply an invalid keychain are ignored. |
The Password and MD5 authentication types also have an additional option that allows for setting the authentication password or keychain associated with the device and line. In the current implementation, the authentication list can only have one item and is a maximum of 16 bytes in length.
