rip2IfConfTable

1.3.6.1.2.1.23.3.1.1

rip2IfConfAddress

IpAddress

read-only

The IP Address of this system on the indicated

subnet. For unnumbered interfaces, the value 0.0.0.N,

where the least significant 24 bits (N) is the ifIndex

for the IP Interface in network byte order.

This object is implemented as defined in the corresponding MIB files.

1.3.6.1.2.1.23.3.1.2

rip2IfConfDomain

OCTET STRING{(2,2)}

read-create

Value inserted into the Routing Domain field

of all RIP packets sent on this interface.

The actually supported access is read-only.

1.3.6.1.2.1.23.3.1.3

rip2IfConfAuthType

INTEGER{noAuthentication(1),simplePassword(2),md5(3)}

read-create

The type of Authentication used on this

interface.

The actually supported access is read-only.

1.3.6.1.2.1.23.3.1.4

rip2IfConfAuthKey

OCTET STRING{(0,16)}

read-create

The value to be used as the Authentication Key

whenever the corresponding instance of

rip2IfConfAuthType has a value other than

noAuthentication. A modification of the corresponding

instance of rip2IfConfAuthType does not modify

the rip2IfConfAuthKey value. If a string shorter

than 16 octets is supplied, it will be left-

justified and padded to 16 octets, on the right,

with nulls (0x00).

Reading this object always results in an OCTET

STRING of length zero; authentication may not

be bypassed by reading the MIB object.

The actually supported access is read-only.

The actually supported value range is 0-16.

1.3.6.1.2.1.23.3.1.5

rip2IfConfSend

INTEGER{doNotSend(1),ripVersion1(2),rip1Compatible(3),ripVersion2(4),ripV1Demand(5),ripV2Demand(6)}

read-create

What the router sends on this interface.

ripVersion1 implies sending RIP updates compliant

with RFC protocols. rip1Compatible implies

broadcasting RIP-2 updates using RFC protocols route

subsumption rules. ripVersion2 implies

multicasting RIP-2 updates. ripV1Demand indicates

the use of Demand RIP on a WAN interface under RIP

Version 1 rules. ripV2Demand indicates the use of

Demand RIP on a WAN interface under Version 2 rules.

The actually supported access is read-only.

1.3.6.1.2.1.23.3.1.6

rip2IfConfReceive

INTEGER{rip1(1),rip2(2),rip1OrRip2(3),doNotRecieve(4)}

read-create

This indicates which version of RIP updates

are to be accepted. Note that rip2 and

rip1OrRip2 implies reception of multicast

packets.

The actually supported access is read-only.

The actually supported value range is rip1(1);rip2(2);rip1OrRip2(3);doNotRecieve(4).

1.3.6.1.2.1.23.3.1.7

rip2IfConfDefaultMetric

INTEGER{(0,15)}

read-create

This variable indicates the metric that is to

be used for the default route entry in RIP updates

originated on this interface. A value of zero

indicates that no default route should be

originated; in this case, a default route via

another router may be propagated.

The actually supported access is read-only.

The actually supported value range is 0-15.

1.3.6.1.2.1.23.3.1.8

rip2IfConfStatus

INTEGER{active(1),notInService(2),notReady(3),createAndGo(4),createAndWait(5),destroy(6)}

read-create

Writing invalid has the effect of deleting

this interface.

The actually supported access is read-only.

The actually supported value range is 0-1.

1.3.6.1.2.1.23.3.1.9

rip2IfConfSrcAddress

IpAddress

read-create

The IP Address this system will use as a source

address on this interface. If it is a numbered

interface, this MUST be the same value as

rip2IfConfAddress. On unnumbered interfaces,

it must be the value of rip2IfConfAddress for

some interface on the system.

The actually supported access is read-only.