CONFIG_NET_IPV6_FRAGMENT_MAX_PKT

How many fragments can be handled to reassemble a packet

Type: int

Help

Incoming fragments are stored in per-packet queue before being
reassembled. This value defines the number of fragments that
can be handled at the same time to reassemble a single packet.

We do not have to accept IPv6 packets larger than 1500 bytes
(RFC 2460 ch 5). This means that we should receive everything
within the first two fragments. The first one being 1280 bytes and
the second one 220 bytes.

You can increase this value if you expect packets with more
than two fragments.

Direct dependencies

NET_IPV6_FRAGMENT && NET_IPV6 && !NET_RAW_MODE && NETWORKING

(Includes any dependencies from ifs and menus.)

Default

• 2

Kconfig definition

At <Zephyr>/subsys/net/ip/Kconfig.ipv6:72

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:44 → <Zephyr>/subsys/Kconfig:39 → <Zephyr>/subsys/net/Kconfig:83 → <Zephyr>/subsys/net/ip/Kconfig:115

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → IP stack → IPv6 → Support IPv6 fragmentation

config NET_IPV6_FRAGMENT_MAX_PKT
    int "How many fragments can be handled to reassemble a packet"
    default 2
    depends on NET_IPV6_FRAGMENT && NET_IPV6 && !NET_RAW_MODE && NETWORKING
    help
      Incoming fragments are stored in per-packet queue before being
      reassembled. This value defines the number of fragments that
      can be handled at the same time to reassemble a single packet.

      We do not have to accept IPv6 packets larger than 1500 bytes
      (RFC 2460 ch 5). This means that we should receive everything
      within the first two fragments. The first one being 1280 bytes and
      the second one 220 bytes.

      You can increase this value if you expect packets with more
      than two fragments.

(The ‘depends on’ condition includes propagated dependencies from ifs and menus.)