How to open port 8444 on TP Link Archer C7 ?

[RollingRoland]

Does anyone have any experience opening port 8444 on a TP Link Archer C7 router ? I added a rule under the option "Port Triggering". That is the closest thing I could find in the router menu. There seems to be no other straight up option to open a port. When I use the checking sites the port 8444 still seems to be closed. So I am not sure if I too dumb to properly set it or if my ISP uses Carrier Grade NAT to put multiple customers behind the same IP address.

My GUI has not been syncing in 24 hours. So any help would be much appreciated.

[dorkmo]

take some screen shots of the router's menu and maybe we can walk you through it.

[RollingRoland]

[RollingRoland]

This is the edit for "Port Triggering"

I also set a Forward Rule:

This is the edit for the "Forward Rule:

[dorkmo]

on that last one, put 8444 in the internal port also i think. you can probably delete the port "triggering" rules

(oh says you can leave blank)

[dorkmo]

you might set up a DHCP reservation for your node computer also to make sure it's network ip address doesnt change

[dorkmo]

What does the "advanced routing" tab show?

[RollingRoland]

Advanced Routing edit:

DHCP settings:

DHCP Address Reservation:

[dorkmo]

click on the DHCP Clients List, you should see all the connected computers, just look for your node. if there is an "add reservation" button that'd be nice. if not copy down the MAC address and create a reservation on that page

[dorkmo]

you could add the google DNS servers to there too https://developers.google.com/speed/public-dns/docs/using

[dorkmo]

https://www.comparitech.com/net-admin/port-forwarding-port-triggering-differences/

https://en.wikipedia.org/wiki/Port_triggering
"It is similar to port forwarding in that it enables incoming traffic to be forwarded to a specific internal host machine, although the forwarded port is not open permanently and the target internal host machine is chosen dynamically"

sounds like you definately want port forwarding, and not port triggering

[sargonas]

Tagging this issue for migration to a discussion. Apologies in advance, but you will be best served by moving this over there and out of the issue tracker, where the community can better assist you. (Ideally the issue tracker should be used to focus on bugs and development problems that need to be addressed, with general user support handled in Discussions and Keybase)

^MigrateToDiscussion