:orphan:

.. title:: NET_TCP_AUTO_ACCEPT

.. option:: CONFIG_NET_TCP_AUTO_ACCEPT

*Auto accept incoming TCP data*

Type: ``bool``

Help
====

Automatically accept incoming TCP data packet to the valid
connection even if the application has not yet called accept().
This speeds up incoming data processing and is done like in Linux.
Drawback is that we allocate data for the incoming packets even if
the application has not yet accepted the connection. If the peer
sends lot of packets, we might run out of memory in this case.

Direct dependencies
===================

\ :option:`NET_TCP <CONFIG_NET_TCP>` && !\ :option:`NET_RAW_MODE <CONFIG_NET_RAW_MODE>` && \ :option:`NETWORKING <CONFIG_NETWORKING>`

*(Includes any dependencies from ifs and menus.)*

Defaults
========

No defaults. Implicitly defaults to ``n``.

Kconfig definition
==================

.. highlight:: kconfig

At ``subsys/net/ip/Kconfig:339``

Included via ``Kconfig:8`` → ``Kconfig.zephyr:34`` → ``subsys/Kconfig:37`` → ``subsys/net/Kconfig:87``

Menu path: (Top) → Sub Systems and OS Services → Networking → Link layer and IP networking support → IP stack → Enable TCP

.. parsed-literal::

    config NET_TCP_AUTO_ACCEPT
    	bool "Auto accept incoming TCP data"
    	depends on \ :option:`NET_TCP <CONFIG_NET_TCP>` && !\ :option:`NET_RAW_MODE <CONFIG_NET_RAW_MODE>` && \ :option:`NETWORKING <CONFIG_NETWORKING>`
    	help
    	  Automatically accept incoming TCP data packet to the valid
    	  connection even if the application has not yet called accept().
    	  This speeds up incoming data processing and is done like in Linux.
    	  Drawback is that we allocate data for the incoming packets even if
    	  the application has not yet accepted the connection. If the peer
    	  sends lot of packets, we might run out of memory in this case.

*(The 'depends on' condition includes propagated dependencies from ifs and menus.)*