I saw some issue with firmware regarding NAT

https://community.tp-link.com/en/business/forum/topic/700604

 

 

maybe this is somehow related??

I am not using any virtual WAN

It doesnt work, as per me seems be issue after upgrade.

 

Ports are closed on device:

 

tplink setup

Hi @DawidR 

Thanks for posting in our business forum.

DawidR wrote

It doesnt work, as per me seems be issue after upgrade.

 

Ports are closed on device:

 

 

tplink setup

 

First, the 443 is taken by the Omada Controller.

Second, I asked you to follow the guide and the guide wrote to post your results.

I want to know what your WAN IP is on the router page. Screenshot needed.

 

Please mosaic your sensitive information. Here is a list of information considered sensitive:

1. Public IP address on your WAN if your WAN is.

2. Real MAC address of your device.

3. Your personal information including address, domain name, and credentials.

For troubleshooting purposes, when a WAN IP is needed, please leave some values visible for identification.

"First, the 443 is taken by the Omada Controller." << But not in case when I dont share admin panel on WAN IP. Everything what I provided ws working on previous firmware, it stopped working after upgrade to 1.3. Telnet is not working, in general none of ports become open on public IP. I can provide some config or logs, but I think this is case which you can try to replicate on Lab for this device

  @Clive_A 

I was on holidays so was not able to handle proper attention on it, but now I am ready to continue this thread.


So my setup is:
ER7212PC 1.0 with firmware 1.3.1 Build 20250220 Rel.67749
I am using NOIP for DNS naming to my public IP (which is non static). 

NOIP is configured on router with domain name: kasprzaka.ddns.net

 

I restarted router and it get new IP assigned, but noip was updated so this layer I have arleady confirmed it is working fine.

 

Next step is to review port availability on router:

So in general my admin UI for router is running on 80/443 but as I have Device Management not enabled it is not present on WAN IP as it is listening just locally on 10.0.0.1 (gateway/router IP).

 

Next thing is going into NAT port forwarding rules I established 3 rules which are enabled:

 

 

So all of them should be working on WAN IP.
Checking locally those IPs:

% curl -skI https://10.0.0.10:4501 |grep HTTP
HTTP/2 200
% curl -skI https://10.0.0.10:443 |grep HTTP
HTTP/2 200
% curl -sI http://10.0.0.10:80|grep HTTP
HTTP/1.1 200 OK

 

so all are responding locally.

 

Lets check does they work thru WANIP and using port forward rules:
 

% curl -sI http://93.159.27.3:80|grep HTTP
^C
% curl -skI https://93.159.27.3:45001 |grep HTTP
^C

 

so they are not responding thru WAN IP.

 

Checking does ports are even open:

 

 

 

 

Telnet commands also not working (timeout):

% telnet 93.159.27.3 45001

Trying 93.159.27.3...

^C
% telnet 93.159.27.3 80
Trying 93.159.27.3...

  @DawidR e

DawidR wrote

  @Clive_A 

I was on holidays so was not able to handle proper attention on it, but now I am ready to continue this thread.


So my setup is:
ER7212PC 1.0 with firmware 1.3.1 Build 20250220 Rel.67749
I am using NOIP for DNS naming to my public IP (which is non static). 

NOIP is configured on router with domain name: kasprzaka.ddns.net

 

 

I restarted router and it get new IP assigned, but noip was updated so this layer I have arleady confirmed it is working fine.

 

Next step is to review port availability on router:
 

So in general my admin UI for router is running on 80/443 but as I have Device Management not enabled it is not present on WAN IP as it is listening just locally on 10.0.0.1 (gateway/router IP).

 

Next thing is going into NAT port forwarding rules I established 3 rules which are enabled:
 

 

 

So all of them should be working on WAN IP.
Checking locally those IPs:

% curl -skI https://10.0.0.10:4501 |grep HTTP
HTTP/2 200
% curl -skI https://10.0.0.10:443 |grep HTTP
HTTP/2 200
% curl -sI http://10.0.0.10:80|grep HTTP
HTTP/1.1 200 OK

 

so all are responding locally.

 

Lets check does they work thru WANIP and using port forward rules:
 

% curl -sI http://93.159.X.Y:80|grep HTTP
^C
% curl -skI https://93.159.X.Y:45001 |grep HTTP
^C

 

so they are not responding thru WAN IP.

 

Checking does ports are even open:

 

 

 

 

 

 

Telnet commands also not working (timeout):

% telnet 93.159.X.Y 45001

Trying 93.159.X.Y...

^C
% telnet 93.159.X.Y 80
Trying 93.159.X.Y...

I have instructed you not to post your WAN IP. I am not responsible for your action in leaking your WAN IP.

I have asked to post your WAN IP info on the router WAN details and mosaic partially, not in this way on a web page. This does not tell the fact if you have the proper setup.

If you don't understand what I am asking, please follow the troubleshooting guide, which tells you what and where you need to check.

 

What I asked is helpful in troubleshooting and correcting your misconfig. If these are not provided, I am not sure I can continue a constructive discussion.