mbedtls_ssl_set_mtu() is only used within mbedTLS.
 
Symbols
loading (4/5)...
Files
loading (4/5)...
SummarySyntaxArgumentsRelatedReferencesData Use

Notes

The limit on datagram size is converted to a limit on record payload by subtracting the current overhead of encapsulation and encryption/authentication if any. This can be called at any point during the connection, for example when a Path Maximum Transfer Unit (PMTU) estimate becomes available from other sources, such as lower (or higher) protocol layers. This setting only controls the size of the packets we send, and does not restrict the size of the datagrams we're willing to receive. Client-side, you can request the server to use smaller records with \c mbedtls_ssl_conf_max_frag_len(). If both a MTU and a maximum fragment length have been configured (or negotiated with the peer), the resulting lower limit on record payload (see first note) is used. This can only be used to decrease the maximum size of datagrams (hence records, see first note) sent. It cannot be used to increase the maximum size of records over the limit set by #MBEDTLS_SSL_OUT_CONTENT_LEN. Values lower than the current record layer expansion will result in an error when trying to send data.

References