@David-TP 

Hello, David.

Thanks for the quick spot on and reply. 

Currently, NE200 is in the test environment (inside), do not care about signal strength. 

Screenshot with IP Passthrough configuration is not the current setting (as it is not working when configured with IP Passthrough). However, you can see from the configuration in the screenshot that I tried to use IP Passthrough. The MAC Address was for the WAN1 port (I also attached the Omada configuration screenshot).

The carrier is Elisa Finland (www.elisa.fi).

I also attached the screenshot showing the assigned public IPv4 (I used a custom APN profile). 

With regards,
Andrew

  @David-TP 

Thanks, David! 

  @RatDiesel 

Hello, I have the same problem with this device and an Omada environment. Please let me know if there's a solution.

  @RatDiesel But this solution is still not forwording the provided IP from the Mobile Carrier just the internal IP from the NE200.

Has anyone found a solution how to get the NE200 in bridge mode.
- Forwording the Mobile Carriers IP to the TP-Link Omada Router ERxxx
- NE200 not having its own DHCP Server (deactivated)

That is very imoprtent to set up a clean and secure VPN Setup for the Omada Network to connect to the network from the outside.

  @David84Omada 

Confirmed working setup (Elisa 5G + NE200 + Omada ER series)
The NE200 now properly forwards the public IP (84.xxx) from Elisa directly to the Omada WAN interface.
No double NAT — Omada receives the same IP as the NE200’s mobile WAN and handles routing, VPN, and DHCP internally.

The NE200 still shows an internal management subnet (192.168.254.x) but it’s isolated and not used for client traffic.

So while TP-Link hasn’t labeled it “bridge mode” in the GUI, the result is full public IP passthrough and a clean single-NAT environment suitable for VPNs and port forwarding.