@Mark_TSB Hi, we have a FORTIGATE firewall in front of TP-LINK, we don't see source <> destination packets. We need to use all TP-LINK features except firewall on all branches.

 

Mark

I disagree @Hank21 :

 Per definition a switch forwards packets at network layer 2: ethernet. A router forwards packets at network layer 3: IP.

 

NAT is not what makes a router a "router". A normal router is stateless an cannot NAT. Tracking connection state is a firewall functionality and thus NAT is also firewall functionality.

 

Residential network gateways that are commonly called routers are usually a combination of a modem (DOCSIS, DSL or PON) a router and a firewall with NAT all in one box. Since the Omada router (I got a TL-R605) does not have a modem I'm forced to use the residential network gateway provided by my ISP and since I only get one public IP I also have to use the NAT functionality of that gateway.

 

I have multiple IP networks/VLANs in my LAN which are routed by the TL-R605. However PC's directly connected to my residential gateway can not reach destinations on the TP-Link part of the network because NAT in the TP-Link Omada solution can not be turned of. There are two possible solutions:

1) Make it possible to disable NAT on a WAN port.

2) Make it possible to set a default route to a device on a LAN port. (Can't do that now. Setting a route to 0.0.0.0/0 fails. The route to 0.0.0.0/0 is the default route)

 

Please

See also https://community.tp-link.com/en/business/forum/topic/257626

  @Mike_E 

Hello

i would also need the possibility to disable NAT in the Router. I have the same use-case as Mike_E.

 

Using a switch is also no solution, because the portalfunction on LAN-Ports needs an Omada Router to work (portal does not take effect if you do the routing on the switch).

With an Ubiquity ER-X you could disable NAT. But for the Omada-world with its gateway and the Portalfunction on LAN-Ports you absolutly need an  Omada Router.

 

Additional info: The main-gateway can't be replaced by the Omadarouter, because of special functions of the main gateway.

 

@Hank21 @Fae,
could you please consider if disabling NAT could get on the roadmap?

 

Greetings

 

 

  @Mark_TSB 

 

This is a big problem. People wanting to switch from ubiquiti platform to omada will most likely not switch because of this.

 

I too have a Roqos RC150 SD Wan Appliance on the edge of my network and have the same problem.

 

Please TP-Link fix this quickly.

 

I should also note that TP-Link router model TL-ER6020 has this ability but it is not omada enabled. See below image.