RIPv2 route entry
see RFC 2453 3.6 and 4
The following diagram shows usage relationships between types. Unresolved types are missing from the diagram.
The following diagram shows inheritance relationships for this type. Unresolved types are missing from the diagram.
Name | Type | Description |
---|---|---|
addressFamilyId | unsigned short |
usually AF_INET (2), but NONE (0) for whole table requests |
routeTag | unsigned short |
0 for RIPv1 |
address | L3Address |
destination address |
prefixLength | int |
prefix length of the destination |
nextHop | L3Address |
next hop address; may be unspecified if the packet is received from the next hop |
metric | unsigned int |
metric of the route (1-15) or infinity (16) if no route to the destination |
// // RIPv2 route entry // // see RFC 2453 3.6 and 4 // struct RIPEntry { unsigned short addressFamilyId @enum(RIP_AF); // usually AF_INET (2), but NONE (0) for whole table requests unsigned short routeTag; // 0 for RIPv1 L3Address address; // destination address int prefixLength; // prefix length of the destination L3Address nextHop; // next hop address; may be unspecified if the packet is received from the next hop unsigned int metric; // metric of the route (1-15) or infinity (16) if no route to the destination }