Routing object that contains the {{object|Router}} table, the received router advertisement information {{object|RouteInformation}}, {{object|Babel}}, and {{object|RIP}} protocol objects. {{numentries}} This object allows the handling of the routing and forwarding configuration of the device. Enables or disables this ''Router'' entry. The status of this ''Router'' entry. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. {{numentries}} {{numentries}} Layer 3 IPv4 forwarding table. In addition to statically configured routes, this table MUST include dynamic routes learned through layer 3 routing protocols, including RIP (i.e. RIP version 2), OSPF, DHCPv4, 3GPP-NAS (3GPP Non Access Stratum) and IPCP. The CPE MAY reject attempts to delete or modify a dynamic route entry. For each incoming packet, the layer 3 forwarding decision is conceptually made as follows: * Only enabled table entries with a matching {{param|ForwardingPolicy}} are considered, i.e. those that either do not specify a {{param|ForwardingPolicy}}, or else specify a {{param|ForwardingPolicy}} that matches that of the incoming packet. * Next, table entries that also have a matching destination address/mask are considered, and the matching entry with the longest prefix is applied to the packet (i.e. the entry with the most specific network). An unspecified destination address is a wild-card and always matches, but with a prefix length of zero. For enabled table entries, if {{param|Interface}} is not a valid reference to an IPv4-capable interface (that is attached to the IPv4 stack), then the table entry is inoperable and the CPE MUST set {{param|Status}} to {{enum|Error_Misconfigured|Status}}. Note: The {{object}} table includes a unique key parameter that is a strong reference. If a strongly referenced object is deleted, the CPE will set the referencing parameter to {{empty}}. However, doing so under these circumstances might cause the updated {{object}} row to then violate the table's unique key constraint; if this occurs, the CPE MUST disable the offending {{object}} row. Enables or disables the forwarding entry. On creation, an entry is disabled by default. Indicates the status of the forwarding entry. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. Specifies the forwarding entry type. Based on {{bibref|RFC8349}} The packet will be sent to the next hop. The packet will be received by the local system. The specified destinations are considered unreachable. Packets are silently discarded. The specified destinations are considered unreachable. Packets are discarded and an ICMP message "host unreachable message" is sent. The specified destinations are considered unreachable. Packets are discarded and an ICMP message "communication administratively prohibited" is sent. If {{true}}, this route is a Static route. Destination IPv4 address. {{empty}} indicates no destination address is specified. A Forwarding table entry for which {{param}} and {{param|DestSubnetMask}} are both {{empty}} is a default route. Destination subnet mask. {{empty}} indicates no destination subnet mask is specified. If a destination subnet mask is specified, the {{param}} is ANDed with the destination address before comparing with the {{param|DestIPAddress}}. Otherwise, the full destination address is used as is. A Forwarding table entry for which {{param|DestIPAddress}} and {{param}} are both {{empty}} is a default route. Identifier of a set of classes or flows that have the corresponding {{param}} value as defined in the {{object|###.QoS}} object. A value of -1 indicates no {{param}} is specified. If specified, this forwarding entry is to apply only to traffic associated with the specified classes and flows. IPv4 address of the gateway. Only one of {{param}} and Interface SHOULD be configured for a route. If both are configured, {{param}} and {{param|Interface}} MUST be consistent with each other. {{reference}} Specifies the egress layer 3 interface associated with this entry. Example: Device.IP.Interface.1. Only one of {{param|GatewayIPAddress}} and {{param}} SHOULD be configured for a route. If both are configured, {{param|GatewayIPAddress}} and {{param}} MUST be consistent with each other. For a route that was configured by setting {{param|GatewayIPAddress}} but not {{param}}, read access to {{param}} MUST return the full hierarchical parameter name for the routes egress interface. Protocol via which the IPv4 forwarding rule was learned. {{enum}} Assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods. e.g. PDU Session Establishment Request, PDN Connectivity Request, PDP Context Activation Request, ... This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP. For example, present in the factory default configuration, created by the Controller, or created by some other management entity (e.g. via a GUI). Forwarding metric. A value of -1 indicates this metric is not used. Layer 3 IPv6 forwarding table. In addition to statically configured routes, this table MUST include dynamic routes learned through layer 3 routing protocols, including RIPng, OSPF, DHCPv6, 3GPP-NAS, and RA. The CPE MAY reject attempts to delete or modify a dynamic route entry. For each incoming packet, the layer 3 forwarding decision is conceptually made as follows: * Only enabled table entries with a matching {{param|ForwardingPolicy}} are considered, i.e. those that either do not specify a {{param|ForwardingPolicy}}, or else specify a {{param|ForwardingPolicy}} that matches that of the incoming packet. * Next, table entries that also have a matching destination prefix are considered, and the matching entry with the longest prefix length is applied to the packet (i.e. the entry with the most specific network). An unspecified destination address is a wild-card and always matches, but with a prefix length of zero. For enabled table entries, if {{param|Interface}} is not a valid reference to an IPv6-capable interface (that is attached to the IPv6 stack), then the table entry is inoperable and the CPE MUST set {{param|Status}} to {{enum|Error_Misconfigured|Status}}. This object is based on ''inetCidrRouteTable'' from {{bibref|RFC4292}}. Enables or disables this {{object}} entry. Indicates the status of the forwarding entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. Specifies the forwarding entry type. Based on {{bibref|RFC8349}} The packet will be sent to the next hop. The packet will be received by the local system. The specified destinations are considered unreachable. Packets are silently discarded. The specified destinations are considered unreachable. Packets are discarded and an ICMP message "host unreachable message" is sent. The specified destinations are considered unreachable. Packets are discarded and an ICMP message "communication administratively prohibited" is sent. Destination IPv6 prefix. {{empty}} indicates that it matches all destination prefixes (i.e. equivalent to "::/0"). All bits to the right of the prefix MUST be zero, e.g. 2001:edff:fe6a:f76::/64. Routes with a 128-bit prefix length (/128) are host routes for a specific IPv6 destination, e.g. 2001:db8:28:2:713e:a426:d167:37ab/128. Identifier of a set of classes or flows that have the corresponding {{param}} value as defined in the {{object|###.QoS}} object. A value of -1 indicates no {{param}} is specified. If specified, this forwarding entry is to apply only to traffic associated with the specified classes and flows. IPv6 address of the next hop. Only one of {{param}} and {{param|Interface}} SHOULD be configured for a route. {{empty}} indicates no {{param}} is specified. If both are configured, {{param}} and {{param|Interface}} MUST be consistent with each other. {{reference}} Specifies the egress layer 3 interface associated with this entry. Example: ''Device.IP.Interface.1''. Only one of {{param|NextHop}} and {{param}} SHOULD be configured for a route. {{empty}} indicates no {{param}} is specified. If both are configured, {{param|NextHop}} and {{param}} MUST be consistent with each other. For a route that was configured by setting {{param|NextHop}} but not {{param}}, read access to {{param}} MUST return the full hierarchical parameter name for the route's egress interface. Protocol via which the IPv6 forwarding rule was learned. {{enum}} Router Advertisement Route Information Option {{bibref|RFC4191}}. RIPng for IPv6 {{bibref|RFC2080}} Address assigned by the core network (fixed or cellular) using 3GPP NAS signalling methods. e.g. PDU Session Establishment Request, PDN Connectivity Request, PDP Context Activation Request, ... This information is available from the AT commands {{bibref|3GPP-TS.27.007|Clause 10.1.23}} PDP context read dynamic parameters +CGCONTRDP. For example, present in the factory default configuration, created by the Controller, or created by some other management entity (e.g. via a GUI). Forwarding metric. A value of -1 indicates this metric is not used. The time at which the route will expire, or {{null}} if not known. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. {{param}} is provided by an underlying dynamic routing protocol, e.g. by an {{bibref|RFC4191}} route information option. Routing Information Protocol (RIP) object. Enables or disables RIP on the device. The supported RIP protocol modes. {{enum}} {{numentries}} IP Interface RIP configuration table. For enabled table entries, if {{param|Interface}} is not a valid reference then the table entry is inoperable and the CPE MUST set {{param|Status}} to {{enum|Error_Misconfigured|Status}}. Note: The {{object}} table includes a unique key parameter that is a strong reference. If a strongly referenced object is deleted, the CPE will set the referencing parameter to {{empty}}. However, doing so under these circumstances might cause the updated {{object}} row to then violate the table's unique key constraint; if this occurs, the CPE MUST set {{param|Status}} to {{enum|Error_Misconfigured|Status}} and disable the offending {{object}} row. Note: This object only applies to RIP2; i.e. version 2 of the RIP protocol is used to accept or send over the specified {{param|Interface}}. Enables or disables this entry. The status of this entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. {{reference}} This is the IP interface associated with this {{object}} entry. When set to {{true}}, RIP route advertisements received over {{param|Interface}} are accepted. When set to {{false}}, RIP route advertisements received over {{param|Interface}} are rejected. When set to {{true}}, RIP route advertisements are to be sent over {{param|Interface}}. When set to {{false}}, no RIP route advertisements will be sent over {{param|Interface}}. Received Router Advertisement (RA) route information {{bibref|RFC4191}}. Enables or disables receiving route information from the RA. {{numentries}} IP Interface RA route information table. Contains received RA route information {{bibref|RFC4191}}. As such, the data in this table cannot be modified. The status of this entry. {{enum}} The {{enum|Error}} value MAY be used by the CPE to indicate a locally defined error condition. {{reference}} This is the IP interface associated with this {{object}} entry. IPv6 Address of the router that sent the RA that included this route info. Flag included in a specific Route Information Option within an RA message (Prf flag), as defined in {{bibref|RFC4191|Section 2.3}}. {{enum}} Note that this is not the Prf flag included in the base RA message. Also see {{bibref|RFC4191|Section 2.1}} which discusses how this flag is encoded on the wire. IPv6 address prefix, as received in an instance of the Route Information Option of a RA message. When set, it indicates that addresses are available via Dynamic Host Configuration Protocol [DHCPv6]. If the {{param}} is set, the {{param|OtherConfiguration}} is redundant and can be ignored because DHCPv6 will return all available configuration information (see {{bibref|RFC4861|Section 4.2}}). When set, it indicates that other configuration information is available via DHCPv6. Examples of such information are DNS-related information or information on other servers within the network (see {{bibref|RFC4861|Section 4.2}}). The time at which {{param|Prefix}} will cease to be usable for use as a forwarding entry, or {{null}} if not known. For an infinite lifetime, the parameter value MUST be 9999-12-31T23:59:59Z. {{param}} is received in an instance of the Route Information Option of a RA message. The time, in {{units}}, that a node assumes a neighbor is reachable after having received a reachability confirmation. Used by the Neighbor Unreachability Detection algorithm {{bibref|RFC4861|see Section 7.3}}. A value of zero means unspecified (by this router) (see {{bibref|RFC4861|Section 4.2}}). The time, in {{units}}, between retransmitted Neighbor Solicitation messages. Used by address resolution and the Neighbor Unreachability Detection algorithm {{bibref|RFC4861|Sections 7.2 and 7.3}}. A value of zero means unspecified (by this router) (see {{bibref|RFC4861|Section 4.2}}). The Home Agent (H) bit is set in a Router Advertisement to indicate that the router sending this Router Advertisement is also functioning as a Mobile IPv6 home agent on this link. (see {{bibref|RFC3775|Section 7.1}} and {{bibref|RFC4861|Section 4.2}}) {{numentries}} This object specifies the received options in a Router Advertisement (RA) message {{bibref|RFC4861|Section 4.6}}. This includes support for receiving DNS information in the RA message as described in {{bibref|RFC6106}}. Option tag (type) {{bibref|RFC4861|Section 4.6}}. A hexbinary encoded option value {{bibref|RFC4861|Section 4.6}}. This object provides parameters for configuration, troubleshooting, and monitoring of the Babel routing protocol {{bibref|RFC8966}}. This data model is based on the Babel information model defined in {{bibref|RFC9046}}. Enables or disables Babel on the device. The status of this entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the device to indicate a locally defined error condition. The name and version of this implementation of the Babel protocol. This is not the same as the version of the Babel protocol that has been implemented. The method of naming and identifying implementation versions will be specific to the implementation. The router-id used by this instance of the Babel protocol to identify itself. {{bibref|RFC8966}} describes this as an arbitrary string of 8 octets. The current sequence number included in route updates for routes originated by this node. Supported cost computation algorithms. {{bibref|RFC8966|Section A.2.1}} {{bibref|RFC8966|Section A.2.2}} Supported security mechanisms. {{bibref|RFC8967}} {{bibref|RFC8968}} Supported MAC computation algorithms. {{bibref|RFC8967}} {{bibref|RFC8967}} Supported DTLS certificate types. {{bibref|RFC8968}} {{bibref|RFC8968}} Enables or disables collection of statistics on all {{object|InterfaceSetting.}} instances. Statistics are provided in {{object|InterfaceSetting.{i}.Stats.}}. When enabled, existing statistics values are not cleared and will be incremented as new packets are counted. {{numentries}} {{numentries}} {{numentries}} {{numentries}} This object represents the constants used by the Babel protocol. The UDP port number used by the Babel implementation to send and receive Babel packets. The UDP port number assigned by IANA is 6696. The multicast group for sending and listening to multicast announcements on IPv6. The multicast group assigned by IANA is ff02::1:6. This object provides parameters related to the interfaces the Babel protocol is operating over and can act as a routing protocol for. Enables or disables Babel on this interface. The status of this entry. {{enum}} The {{enum|Error_Misconfigured}} value indicates that a necessary configuration value is undefined or invalid. The {{enum|Error}} value MAY be used by the device to indicate a locally defined error condition. The {{object|###.IP.Interface}} object instance this Babel implementation is running over. The referenced interface object MUST have {{param|###.IP.Interface.{i}.IPv6Enable}} set to true. Indicates the metric computation algorithm used on this interface, from among the supported metric computation algorithms listed in {{param|#.SupportedMetricCompAlgorithms}}. Enables or disables the use of split horizon optimization when calculating metrics on this interface. Split horizon optimization is described in {{bibref|RFC8966|Section 3.7.4}}. The current sequence number in use for multicast Hellos sent on this interface. The current interval (time in {{units}}) used for multicast Hellos sent on this interface. The current interval (time in {{units}}) used for all updates (multicast or unicast) sent on this interface. Enables or disables the MAC security mechanism. {{object|#.MACKeySet.}} instances that apply to this {{object}} instance. When an {{object}} is created, all {{object|#.MACKeySet.}} instances with {{param|#.MACKeySet.{i}.DefaultApply}} of {{true}} will be included in this list. A Boolean flag indicating whether MACs in incoming Babel packets are required to be present and are verified. If this parameter is {{true}}, incoming packets are required to have a valid MAC. Enables or disables the DTLS security mechanism. {{object|#.DTLSCertSet.}} instances that apply to this {{object}} instance. When an {{object}} is created, all {{object|#.DTLSCertSet.}} instances with {{param|#.DTLSCertSet.{i}.DefaultApply}} of {{true}} will be included in this list. A Boolean flag indicating whether the cached_info extension is included in ClientHello and ServerHello packets (see {{bibref|RFC8968|Appendix A}}. The extension is included if {{true}}. Supported certificate types (from {{param|#.SupportedDTLSCertTypes}}), listed in order of preference. This list is used to populate the server_certificate_type extension in a ClientHello (see {{bibref|RFC8968|Appendix A}}). Values that are present with a non-empty {{param|#.DTLSCertSet.{i}.DTLSCert.{i}.CertPrivateKey}} in at least one instance of {{object|#.DTLSCertSet.{i}.DTLSCert.}} included in a {{object|#.DTLSCertSet.}} instance referenced by {{param|InterfaceDTLSCertSets}} will be used to populate the client_certificate_type extension in a Client Hello. Enables or disables the logging of Babel packets into the {{param|PacketLog}} on this interface. A reference to a {{object|###.DeviceInfo.VendorLogFile}} instance that contains a timestamped log of packets received and sent on {{param|#.Constants.UDPPort}} on this interface. The {{bibref|LIBPCAP}} file format with .pcap file extension SHOULD be supported for packet log files. Logging is enabled/disabled by {{param|PacketLogEnable}}. {{numentries}} This object provides statistics parameters for this interface. A count of the number of multicast Hello packets sent on this interface. A count of the number of multicast update packets sent on this interface. A count of the number of unicast Hello packets sent on this interface. A count of the number of unicast update packets sent on this interface. A count of the number of IHU ("I Heard You") packets sent on this interface. A count of the number of Babel packets received on this interface. This object provides parameters related to neighbor devices that Babel packets are received from and sent to. IP address the neighbor sends packets from. The multicast Hello history of whether or not the multicast Hello packets prior to {{param|ExpectedMCastHelloSeqno}} were received. This is a binary sequence where the most recently received Hello is expressed as a "1" placed in the left-most bit, with prior bits shifted right (and "0" bits placed between prior Hello bits and the most recent Hello bit for any not-received Hellos). This value is displayed using hex digits. See {{bibref|RFC8966|Section A.1}}. The unicast Hello history of whether or not the unicast Hello packets prior to {{param|ExpectedUCastHelloSeqno}} were received. This is a binary sequence where the most recently received Hello is expressed as a "1" placed in the left-most bit, with prior bits shifted right (and "0" bits placed between prior Hello bitss and the most recent Hello bit for any not-received Hellos). This value is displayed using hex digits. See {{bibref|RFC8966|Section A.1}}. Transmission cost value from the last IHU ("I Heard You") packet received from this neighbor, or maximum value (as defined in {{bibref|RFC8966|Section 3.4.2}}) to indicate the IHU hold timer for this neighbor has expired. Expected multicast Hello sequence number of next Hello to be received from this neighbor. If multicast Hello packets are not expected, or processing of multicast packets is not enabled, this MUST be -1. Note {{bibref|RFC9046}} specifies a 16-bit unsigned integer with NULL value to represent no processed or expected multicast Hello packets. Expected unicast Hello sequence number of next Hello to be received from this neighbor. If unicast Hello packets are not expected, or processing of unicast packets is not enabled, this MUST be -1. The current sequence number in use for unicast Hellos sent to this neighbor. If unicast Hello packets are not being sent, this MUST be -1. The current interval in {{units}} used for unicast Hellos sent to this neighbor. Reception cost calculated for this neighbor. This value is usually derived from the Hello history, which may be combined with other data, such as statistics maintained by the link layer. The {{param}} is sent to a neighbor in each IHU ("I Heard You") packet. See {{bibref|RFC8966|Section 3.4.3}}. Link cost is computed from the values maintained by a Babel implementation in its neighbor table as defined in {{bibref|RFC8966|Section3.2.4}}: the statistics kept about the reception of Hellos and the transmission cost computed from received IHU packets. See {{bibref|RFC8966|Section 3.4.3}}. This object provides parameters for routes received from neighbors and internal routes. IP prefix for which this route is advertised. Router-id of the router that originated this route. Reference to the {{object|#.InterfaceSetting.{i}.Neighbor}} entry for the neighbor that advertised this route. The metric with which this route was advertised by the neighbor, or maximum value (as defined in {{bibref|RFC8966}}) to indicate the route was recently retracted and is temporarily unreachable (see {{bibref|RFC8966|Section 3.5.5}}). This metric will be -1 if the route was not received from a neighbor but was generated through other means. At least one of {{param}} and {{param|CalculatedMetric}} MUST have a value other than -1. Having both be other than -1 is expected for a route that is received and subsequently advertised. A calculated metric for this route. How the metric is calculated is implementation-specific. Maximum value (as defined in {{bibref|RFC8966}}) indicates the route was recently retracted and is temporarily unreachable ({{bibref|RFC8966|Section 3.5.5}}). At least one of {{param|ReceivedMetric}} and {{param}} MUST have a value other than -1. Having both be other than -1 is expected for a route that is received and subsequently advertised. The sequence number with which this route was advertised. The next-hop address of this route. This will be empty if this route has no next-hop address. A Boolean flag indicating whether this route is feasible, as defined in {{bibref|RFC8966|Section 3.5.1}}. A Boolean flag indicating whether this route is selected (i.e., whether it is currently being used for forwarding and is being advertised). This object provides parameters related to use of the HMAC security mechanism {{bibref|RFC8967}} to sign and verify Babel packets. A Boolean flag indicating whether this {{object}} instance is to be applied to all new {{object|#.InterfaceSetting.}} instances. If {{true}}, this {{object}} instance applies to all new {{object|#.InterfaceSetting.}} instances at the time they are created and a reference to this {{object}} is included in the {{param|#.InterfaceSetting.{i}.InterfaceMACKeySets}} parameter. If {{false}}, this {{object}} is not applied to new {{object|#.InterfaceSetting.}} instances when they are created. {{numentries}} This object provides the MAC keys used to calculate MACs for verification and sending by the {{object|#.}} instance. Indicates whether this {{param|KeyValue}} is used to compute a MAC and include that MAC in the sent Babel packet. A MAC for sent packets is computed using this key if the value is {{true}}. If the value is {{false}}, this key is not used to compute a MAC to include in sent Babel packets. Indicates whether the {{param|KeyValue}} is used to verify incoming Babel packets. Incoming packets are verified using this key if {{true}}. If {{false}} no MAC is computed from {{param|KeyValue}} for comparing with the MAC in an incoming Babel packet. The value of the MAC key. This value is immutable, once written. This value is of a length suitable for the associated {{param|MACKeyAlgorithm}}. If the algorithm is based on the HMAC construction {{bibref|RFC2104}}, the length MUST be between 0 and an upper limit that is at least the size of the output length (where "HMAC-SHA256" output length is 32 octets as described in {{bibref|RFC4868}}). Longer lengths MAY be supported but are not necessary if the management system has the ability to generate a suitably random value (e.g., by randomly generating a value or by using a key derivation technique as recommended in {{bibref|RFC8967|Security Considerations}}). If the algorithm is "BLAKE2s-128", the length MUST be between 0 and 32 bytes inclusive, as specified in {{bibref|RFC7693}}. The name of the MAC algorithm used with this key. The value MUST be the same as one of the enumerations listed in the {{param|##.SupportedMACAlgorithms}} parameter. This object provides parameters related to use of the DTLS security mechanism {{bibref|RFC8968}} to encrypt Babel packets. A Boolean flag indicating whether this {{object}} instance is to be applied to all new {{object|#.InterfaceSetting.}} instances. If {{true}}, this {{object}} instance applies to all new {{object|#.InterfaceSetting.}} instances at the time they are created and a reference to this {{object}} is included in the {{param|#.InterfaceSetting.{i}.InterfaceDTLSCertSets}} parameter. If {{false}}, this {{object}} is not applied to new {{object|#.InterfaceSetting.}} instances when they are created. {{numentries}} This object provides the certificates used for verification and signing by the {{object|#.}} instance with DTLS. The DTLS certificate in PEM format {{bibref|RFC7468}}. This value is immutable, once written. The certificate type of {{param|CertValue}} (from among the supported types in {{param|##.SupportedDTLSCertTypes}}). This value is immutable, once written. The private key of the certificate. {{param}} is only given a value if the certificate belongs to this device. If {{param}} is non-empty, this certificate can be supplied during DTLS handshaking. This value is immutable, once written.