Help¶

Call mbedtls_ssl_conf_max_frag_len() on created TLS context configuration, so that Maximum Fragment Length (MFL) will be sent to peer using RFC 6066 max_fragment_length extension.

Maximum Fragment Length (MFL) value is automatically chosen based on MBEDTLS_SSL_OUT_CONTENT_LEN and MBEDTLS_SSL_IN_CONTENT_LEN mbed TLS macros (which are configured by CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN in case of default mbed TLS config).

This is mostly useful for TLS client side to tell TLS server what is the maximum supported receive record length.

Direct dependencies¶

NET_SOCKETS && NETWORKING

(Includes any dependencies from ifs and menus.)

Default¶

y

Kconfig definition¶

At <Zephyr>/subsys/net/lib/sockets/Kconfig:57

Included via <Zephyr>/Kconfig:8 → <Zephyr>/Kconfig.zephyr:34 → <Zephyr>/subsys/Kconfig:34 → <Zephyr>/subsys/net/Kconfig:89 → <Zephyr>/subsys/net/lib/Kconfig:30

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → Network Libraries → BSD Sockets compatible API

config NET_SOCKETS_TLS_SET_MAX_FRAGMENT_LENGTH
    bool "Set Maximum Fragment Length (MFL)"
    default y
    depends on NET_SOCKETS && NETWORKING
    help
      Call mbedtls_ssl_conf_max_frag_len() on created TLS context
      configuration, so that Maximum Fragment Length (MFL) will be sent to
      peer using RFC 6066 max_fragment_length extension.

      Maximum Fragment Length (MFL) value is automatically chosen based on
      MBEDTLS_SSL_OUT_CONTENT_LEN and MBEDTLS_SSL_IN_CONTENT_LEN mbed TLS
      macros (which are configured by CONFIG_MBEDTLS_SSL_MAX_CONTENT_LEN in
      case of default mbed TLS config).

      This is mostly useful for TLS client side to tell TLS server what is
      the maximum supported receive record length.

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