networking/devlink/devlink-trap.rst

21 kernel so that it will route it as well and generate an ICMP Time Exceeded
39 as it allows users to obtain further visibility into packet drops that would
123 Generic packet traps are used to describe traps that trap well-defined packets
124 or packets that are trapped due to well-defined conditions (e.g., TTL error).
136      - Traps incoming packets that the device decided to drop because of a
140      - Traps incoming packets that the device decided to drop in case of VLAN
145      - Traps incoming packets that the device decided to drop in case they are
146        tagged with a VLAN that is not configured on the ingress bridge port
149      - Traps incoming packets that the device decided to drop in case the STP
153      - Traps packets that the device decided to drop in case they need to be
158      - Traps packets that the device decided to drop in case after layer 2
163      - Traps packets that the device decided to drop in case they hit a
167      - Traps unicast packets that should be forwarded by the device whose TTL
171      - Traps packets that the device decided to drop because they could not be
175      - Traps packets that the device decided to drop because they need to
179      - Traps packets that the device decided to drop because they need to be
184      - Traps packets that the device decided to drop because they need to be
189      - Traps packets that the device decided to drop because they need to be
193      - Traps packets that the device decided to drop because they need to be
197      - Traps packets that the device decided to drop because they need to be
202      - Traps packets that the device decided to drop because they need to be
206      - Traps IPv6 packets that the device decided to drop because they need to
211      - Traps IPv6 packets that the device decided to drop because they need to
216      - Traps packets that should have been routed by the device, but were bigger
220      - Traps packets that did not have a matching IP neighbour after routing
223      - Traps multicast IP packets that failed reverse-path forwarding (RPF)
227      - Traps packets that hit reject routes (i.e., "unreachable", "prohibit")
230      - Traps unicast IPv4 packets that did not match any route
233      - Traps unicast IPv6 packets that did not match any route
236      - Traps packets that the device decided to drop because they are not
242      - Traps NVE and IPinIP packets that the device decided to drop because of
247      - Traps NVE packets that the device decided to drop because their overlay
305      - Traps NVE-decapsulated ARP packets that reached the overlay network.
306        This is required, for example, when the address that needs to be
346      - Traps unicast packets that need to be routed through the same layer 3
351      - Traps unicast packets that hit a local route and need to be locally
355      - Traps packets that should be routed through an external interface (e.g.,
356        management interface) that does not belong to the same device (e.g.,
360      - Traps unicast IPv6 packets that need to be routed and have a destination
366      - Traps IPv6 packets that their destination IP address is the "All Nodes
370      - Traps IPv6 packets that their destination IP address is the "All Routers
383      - Traps IPv4 packets that need to be routed and include the Router Alert
384        option. Such packets need to be locally delivered to raw sockets that
388      - Traps IPv6 packets that need to be routed and include the Router Alert
390        locally delivered to raw sockets that have the IPV6_ROUTER_ALERT socket
468        This would mean that port number 0 was used or that the header is
481      - Traps packets that the device decided to drop in case they hit a
485      - Traps incoming packets that the device decided to drop because
494      - Traps packets that the device decided to drop because they failed the
495        locked bridge port check. That is, packets that were received via a
529      - Contains packet traps for packets that were dropped by the device during
532      - Contains packet traps for packets that were dropped by the device during
535      - Contains packet traps for packets that hit an exception (e.g., TTL
538      - Contains packet traps for packets that were dropped by the device due to
541      - Contains packet traps for packets that were dropped by the device during
544      - Contains packet traps for packets that were dropped by the device during
577      - Contains packet traps for packets that should be locally delivered after
581      - Contains packet traps for packets that should be routed through an
582        external interface (e.g., management interface) that does not belong to
594      - Contains packet traps for packets that were sampled by the device during
597      - Contains packet traps for packets that were trapped (logged) by the
600      - Contains packet traps for packets that were marked by the device during
611 packet rates that are several orders of magnitude higher compared to those that
615 devices usually include packet trap policers that are able to police the
616 trapped packets to rates that can be handled by the CPU.
628 If possible, device drivers should implement a callback that allows user space
629 to retrieve the number of packets that were dropped by the policer because its