ER7206 VF Kabel Portforwarding

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

ER7206 VF Kabel Portforwarding

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
ER7206 VF Kabel Portforwarding
ER7206 VF Kabel Portforwarding
2022-08-09 06:29:13 - last edited 2022-08-10 02:30:08
Model: ER7206 (TL-ER7206)  
Hardware Version: V1
Firmware Version: 1.2.1

HI,

 

I recently baught the HW for the replacements of my unifi network.

 

The OC200 is replaced by the dockerized version of Omada SDN and running on the latest version as well from mbentley/omada-controller.

 

So far everything runs with great stability and performance, hence I have a serious problem with the portforwarding.

 

I have a nextcloud running inside my network and need to expose the 443 port, this is absolutely must, to have this accessible from anywhere, nothing else.

 

So I configured for testing also the port 80 as well as 443, but still none of these ports are open on the WAN side.

 

I also tried to put the internal IP into a DMZ zone, not working as well.

 

I could not find any log files for htis operation, is there a reasonable way, to find some logs here to check whats the reason, why this PFWD does not work?

 

Thanks and BRs

  0      
  0      
#1
Options
1 Accepted Solution
Re:ER7206 VF Kabel Portforwarding-Solution
2022-08-09 07:40:34 - last edited 2022-08-10 02:30:08
completely my fault, the requested host runs on a proxmox server as a vm and I changed the ip and routing of the host, still the default route of the vm pointed to the old gw, changed this and everything is fine now
Recommended Solution
  4  
  4  
#3
Options
2 Reply
Re:ER7206 VF Kabel Portforwarding
2022-08-09 07:16:26
opening another port on the controller to a well know ip works. So I assume, it peforms some background checks before really opening it. Seems not to be related to the ER
  0  
  0  
#2
Options
Re:ER7206 VF Kabel Portforwarding-Solution
2022-08-09 07:40:34 - last edited 2022-08-10 02:30:08
completely my fault, the requested host runs on a proxmox server as a vm and I changed the ip and routing of the host, still the default route of the vm pointed to the old gw, changed this and everything is fine now
Recommended Solution
  4  
  4  
#3
Options