Port Forwarding Issue On TP-Link ER707-M2 Omada
Port Forwarding Issue On TP-Link ER707-M2 Omada
Hello,
I recently started the move from Synology router to Tp-Link Omada solution.
I have different services in my network like Nginx & Bitwarden....
I try to put in ln place port opening (80-443-8181) for Nginx, and port forwarding.
As far As i understood the port forwarding in TP-link should open the port (80-443-8181) in the firewall once created. I did 3 new rules in Transmission/NAT/port forwarding.
I'm facing issue because all ports are still closed in my public WAN ip .
Thanks a lot in advanced for your help
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Thanks for posting in our business forum.
If you can give the screenshots for your steps/results by following this guide.
Mosaic your sensitive information but make it still readable to tell your IP class.
So next time if you need help from me, it is also best for you to include the pictures. I don't rely on the word description unless I witness what you configured and confirm them correct.
- Copy Link
- Report Inappropriate Content
Hello,
My router is in V1.0 then the controller i have is the last.
I'm trying to understand as, seems it's working now.
I assume the router open port in the firewall only if the service to forward the port works, and as i was in maintenance in my nginx the docker was stopped.
Then it should be ok.
Thanks to all of you.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Hello ,
Thanks for your response.
Yes I did one per port, and ports are always closed
I don't know what. to do more.
Rgds
- Copy Link
- Report Inappropriate Content
I have several port NATs on the ER707-M2 which all work as they should. what you have to watch out for is that the router is not behind another router. then it will be double NAT, if you have another router, you must also do NAT there as well.
so the router must have a public IP on the WAN or you must also do NAT in the router that has the WAN IP.
if you have created ACLs, delete them. that's not necessary
- Copy Link
- Report Inappropriate Content
Thanks for posting in our business forum.
First, both replies from others are correct. They have at least verified it is not the firmware issue.
Filter, Troubleshooting, and you can find this article helpful:
- Copy Link
- Report Inappropriate Content
Hello @MR.S
Thanks for your feedback.
My router have no ACL rule set . It's connected directly in my Pon box (fiber ethernet output )to the router ER707-M2 who have a direct access to internet. No boy of my isp provider.
Ip of the connection also checked and ok.
... :-(
- Copy Link
- Report Inappropriate Content
what happens if you go to https://yorpublicip from a computer that is in same lan as device you try NAT to?
do you get access?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Ok, I think @Clive_A have to look at this, for me all look right.
as I mention I have a ER707-M2 myself and portforward work as it should.. I forwared many different port and no problem with this.
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2235
Replies: 14
Voters 0
No one has voted for it yet.