alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity

Merge branch 'lwip/napt_doc_menu_modify' into 'master'

Browse Source 
change(lwip): Remove 'experimental' from NAPT in kconfig, update lwIP doc

See merge request espressif/esp-idf!27849
This commit is contained in:
Abhik Roy 2024-02-01 21:15:53 +08:00
commit a6e2c52a43
2 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
components/lwip/Kconfig
View File

@ -248,14 +248,14 @@ menu "LWIP"
Enabling this option allows packets forwarding across multiple interfaces.
config LWIP_IPV4_NAPT
bool "Enable NAT (new/experimental)"
bool "Enable NAT"
depends on LWIP_IP_FORWARD
default n
help
Enabling this option allows Network Address and Port Translation.
config LWIP_IPV4_NAPT_PORTMAP
bool "Enable NAT Port Mapping (new/experimental)"
bool "Enable NAT Port Mapping"
depends on LWIP_IPV4_NAPT
default y
help

8
docs/en/api-guides/lwip.rst
View File

@ -419,6 +419,14 @@ IP Layer Features
- IPV4-mapped IPV6 addresses are supported
NAPT and Port Forwarding
++++++++++++++++++++++++
IPV4 network address port translation (NAPT) and port forwarding are supported. However, the enabling of NAPT is limited to a single interface.
- To use NAPT for forwarding packets between two interfaces, it needs to be enabled on the interface connecting to the target network. For example, to enable internet access for Ethernet traffic through the WiFi interface, NAPT must be enabled on the Ethernet interface.
- Usage of NAPT is demonstrated in :example:`network/vlan_support`.
.. _lwip-custom-hooks:
Customized lwIP Hooks