struct MD5PacketRouteEntry4 Route Entry for MD5 data. More... Definition #include <packets.hh> List of all Methods

Annotated List Files Globals Hierarchy Index

Public Methods

• inline uint16_t  addr_family () const
• inline uint16_t  auth_type () const
• inline uint16_t  auth_offset () const
• inline uint8_t  key_id () const
• inline uint8_t  auth_bytes () const
• inline uint32_t  seqno () const
• inline void  set_auth_offset (uint16_t b)
• inline void  set_key_id (uint8_t id)
• inline void  set_auth_bytes (uint8_t b)
• inline void  set_seqno (uint32_t sno)
• inline void  initialize (uint16_t pkt_bytes, uint8_t key_id, uint8_t auth_bytes, uint32_t seqno)
• inline void  initialize (uint16_t auth_offset, uint8_t key_id, uint8_t auth_bytes, uint32_t seqno)

Public Members

• static const uint16_t ADDR_FAMILY
• static const uint16_t AUTH_TYPE

Protected Members

• uint16_t _af
• uint16_t _auth
• uint16_t _auth_offset
• uint8_t _key_id
• uint8_t _auth_bytes
• uint32_t _seqno
• uint32_t _mbz[2]

Detailed Description

The MD5PacketRouteEntry4 may appear as the first route entry in a RIPv2 packet. It has the same size as an PacketRouteEntry<IPv4>. The address family has the special value 0xffff which imples authentication. The authentication type is overlaid in the route tag field and takes the special value 3. With MD5 the authentication data appears after the remaining route entries. Details are disclosed in RFC2082.

All items in the route entry are stored in network order. The accessor methods provide values in host order, and the modifiers take arguments in host order.

NB We describe the field labelled as "RIP-2 Packet Length" on page 5 of RFC 2082 as the "auth_offset". This matches the textual description in the RFC.

[protected]

[protected]

[protected]

[protected]

[protected]

[protected]

[protected]

[const]

[const]

[const]

[const]

[const]

[const]