How to Disable NAT on Omada Gateway

ER7206( V2 V2.2 ) , ER7406( V1 ) , ER706W( V1 ) , ER605( V2.2 )
Recent updates may have expanded access to feature(s) discussed in this FAQ. Visit your product's support page, select the correct hardware version for your device, and check either the Datasheet or the firmware section for the latest improvements added to your product. Please note that product availability varies by region, and certain models may not be available in your region.
Contents
Objective
This article provides a practical guide for configuring the Disable NAT feature on Omada Gateway devices, making it easy for users to implement.
Requirements
- Omada Controller (software Controller v5.15.20)
- Omada Gateway ER7206 v2.0
Introduction
By default, when NAT is enabled on the Omada Gateway, traffic from the WAN to the LAN is restricted, which can make it difficult for external devices to access internal resources. The new Disable NAT feature, introduced in SDNC 5.15, allows WAN-to-LAN traffic to be forwarded directly without NAT translation, enabling public network devices to reach internal LAN servers and services.
Configuration
This section explains how to configure Virtual WAN for dedicated line service scenarios.
Step 1. Log in to the controller management page, navigate to Settings > NAT > Disable NAT, and click Create New Rule to add a Disable NAT rule.
Step 2. When configuring the Disable NAT rule, select the physical WAN port under the Interface option (for example, WAN2). For the LAN setting, select one or more LAN networks depending on your requirements.
Note:
- A single WAN port supports the configuration of only one Disable NAT rule.
- When creating a Disable NAT rule, a priority mode policy routing rule will be automatically generated by default to bind the corresponding WAN port and LAN network. The priority mode policy routing rule is depend upon the online detection status of the WAN port, and it will only take effect if the result is online.
Verification
You can use Wireshark to compare the packet differences between NAT and Disable NAT scenarios. This will demonstrate how packets change as they travel from the LAN to the WAN port when Disable NAT is enabled.
Scenario One: Disable NAT not enabled
Run "ping 192.168.0.1" on the PC and perform packet capture on the LAN port of Gateway-A (connected to Gateway-B). The following results are observed:
Scenario Two: Disable NAT and add a static route to 192.168.10.X/24 on the middle router, with the next hop set to 192.168.0.100.
Create a static route as follow. All traffic to 192.168.10.X/24 subnet will be routed to 192.168.0.100 as the next hop. Repeat the same test as in Scenario One.
After enabling Disable NAT, the packet capture on LAN port of the left gateway will show the PC’s actual IP address as the source. This confirms that packets are no longer translated by NAT. In this scenario, the middle gateway works as a Layer 3 switch, and upstream devices can see the real client IP for more flexible policy control.
Conclusion
The preceding text has introduced the configuration steps for Disable NAT on the Omada Gateway series models compatible with the SDNC 5.15 software version.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
¿Es útil esta pregunta frecuente?
Sus comentarios nos ayudan a mejorar este sitio.
¿Cuál es tu preocupación con este artículo?
- Insatisfecho con el producto
- Muy complicado
- Titulo confuso
- Eso no aplica a mi
- Demasiado vago
- Otro
Gracias
Agradecemos sus comentarios.
Haga clic aquí para comunicarse con el soporte técnico de TP-Link.
Recommend Products
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Your Privacy Choices
Este sitio utiliza cookies. Si continúa navegando por el sitio, acepta el uso que hacemos de las cookies. No volver a mostrar Más información .
Cookies basicas
TP-Link
SESSION, JSESSIONID, accepted_local_switcher, tp_privacy_banner, tp_privacy_base, tp_privacy_marketing, tp_top-banner, tp_popup-bottom, tp_popup-center, tp_popup-right-middle, tp_popup-right-bottom, tp_productCategoryType
Youtube
id, VISITOR_INFO1_LIVE, LOGIN_INFO, SIDCC, SAPISID, APISID, SSID, SID, YSC, __Secure-1PSID, __Secure-1PAPISID, __Secure-1PSIDCC, __Secure-3PSID, __Secure-3PAPISID, __Secure-3PSIDCC, 1P_JAR, AEC, NID, OTZ
Zendesk
OptanonConsent, __cf_bm, __cfruid, _cfuvid, _help_center_session, _pendo___sg__.<container-id>, _pendo_meta.<container-id>, _pendo_visitorId.<container-id>, _zendesk_authenticated, _zendesk_cookie, _zendesk_session, _zendesk_shared_session, ajs_anonymous_id, cf_clearance
Cookies de análisis y marketing
Las cookies de análisis nos permiten analizar sus actividades en nuestro sitio web para mejorar y adaptar la funcionalidad de nuestro sitio web.
Nuestros socios publicitarios pueden configurar las cookies de marketing a través de nuestro sitio web para crear un perfil de sus intereses y mostrarle anuncios relevantes en otros sitios web.
Google Analytics y Google Tag Manager
_gid, _ga_<container-id>, _ga, _gat_gtag_<container-id>
Google Ads y DoubleClick
test_cookie, _gcl_au