Business Community > All Threads > Unable to route port 80/443 through NAT/DMZ
< All Threads

Unable to route port 80/443 through NAT/DMZ

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Unable to route port 80/443 through NAT/DMZ

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Unable to route port 80/443 through NAT/DMZ
Unable to route port 80/443 through NAT/DMZ
2022-11-21 15:01:05
Tags: #NAT #Firmware Update
Model: TL-ER5120  
Hardware Version: V3
Firmware Version: TL-ER5120(UN)_V3_20200313

Hello,

 

The latest firmware, TL-ER5120(UN)_V3_20200313, does not work with standard ports such as port 80 and port 443.

 

When NAT-DMZ is set, everything but standard ports are relayed.

 

Rolling back to TL-ER5120(UN)_V3_20180830 the problem cease to exists.

 

I wasted a lot of hours in diagnosticating this issue - and it could be a bit somewhere in the updated firmware I failed to see.

 

But rolling back to previous firmware fixes my issue - but I do have concerns about security.

 

Please, if at all possible, update your firmware or provide guidance to new functionality that block default ports by standard.

 

Thanks.

 

Best regards,


Michael

  0      
 
  0      
 
#1
Options
2 Reply
Re:Unable to route port 80/443 through NAT/DMZ
2022-11-22 11:35:59

  @gimlichael 

 

Ports 80 and 443 should be open by default within the LAN, you can test it if you try to access it from the WAN side, it is still inaccessible, after all it is a NAT device.

Just striving to develop myself while helping others.
  0  
  0  
#2
Options
Re:Unable to route port 80/443 through NAT/DMZ
2022-11-22 21:35:19

  @Virgo as I wrote; I did an intensive testing.


After updating from previous firmware, things started to fail (most services I run are 80/443).

Doing NAT from second router (which is where the DMZ NAT points to), I changed original routing point to my workstation.

Here I spun up a docker test image, exposing various ports.

All ports but 80/443 worked as expected.

 

After downgrading the firmware, I repeated the above mentioned.

 

Now everything works as expected - also on 80/443.

  0  
  0  
#3
Options

Information

Helpful: 0

Views: 528

Replies: 2

Tags

NAT Firmware Update
Related Articles
Exposing my port 80 and 443 via the Omada Software Controller for hosting Nginx reverse proxy
2314 0
Port Forwarding 443 Forwards to the WebUI of the Router Instead of the Internal Server
2148 0
NAT does not work if input and output port are different
616 0
Change the port to 443 in OpenVPN
544 0
Omada software controller 4.1.5 - Port 80 and port 443 are already in use
3525 0
Unable to port forward ports 465 and 587
1352 0
About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.