Hello and welcome to Just Answer! My name is Josh and I would be glad to help you.
Port trigger works in a manner where you define a specified destination port (trigger range) and a defined forwarding port. When the router sees traffic destined for that destination port, it opens up forwarding for the forwarding port. In your example when an outbound packet is destined for an IP address on port 50 then the router will forward port 80 inbound from the internet to the same host that sent the original packet destined for port 50.
There is no port redirection or translation as your original question implies.
So basically if you have port 50 in the triggered range and have port 80 in the forwarded range then I am assuming that port 50 is going contact the remote computer on then internet and it is going to send data through port 80 right.
You're assuming that the application on the remote computer on the internet has a need to send traffic back to port 80 but this isn't to misunderstood as the router is going to force traffic back through port 80.
So if the application has no need to send traffic back to port 80 then the whole function really is pointless.
Please give me a few minutes. Thank you
Take your time. I will be here for a little while and feel free to ask any further questions.
I've noticed you have been asking a lot of networking questions as of late. Are you studying for a certain career?
Oh really, and what is that?
computer software and repair
I am thinking that when you have port triggering enabled on a router that when you have port 50 in the triggered range and have port 80 in the forwarded range that when you get on the internet the triggered range is going to use port 50 under the triggered range to connect to the remote computer on the internet to send data through port 80 to the Ip address of the computer.
No that's not the case. It should simply just open up that port.
Open the port for what
do you mean to open the port for port 80
It will open up the "forwarding port" to be accessible inbound from the internet.
Yes in your example, port 80
But that doesn't mean that all reply traffic is forced through port 80. It just makes it available.
So for example if you set the trigger range to have port 53 and the forwarding port to 80 then that would be pointless. This is because port 53 is DNS. By default a DNS server would have no use in being able to connect back to you on port 80. It would continue to operate on the PAT ports.
The only reason the "forwarding port" would be of use is if the remote server/PC you are connecting to had a need to come back on that port.
So you are saying that if a particular port say for example port 50 wants to send data through port 80, then it will open port 80 back up in order for port 50 to send the data through port 80 right.
Yes. But more correctly it would be worded as "particular [application listening on] port 50 wants to send return traffic to port 80 , then it [the router] will already have port 80 opened in order for [the application running on] port 50 to send the data back on port 80"
See, usually ports are protocol specific. IE 53 is DNS, 80 is HTTP, etc. So what would be happening in the background on the remote PC is that the application running on port 50 would most likely be sending HTTP traffic back to you for some reason.
Let me rephrase the question to make sure that I understand the question
OK. Sorry if I'm confusing you. It's kind of a situational question.
So for example If I have port 49 in the triggered range and have port 80 in the forward range and when I get ready to access the remote computer on the internet the router is going to use port 49 to open the forward range port for port 80 to allow data to come through port 80 to the Ip address of the computer right.
But if there is no more data coming from port 49 then it will close port 80 right.
Ok let me explain this another way.
Look at port 49 and 80 as two completely seperate things to the router.
The router doesn't care if/who/what comes back on port 80. It also doesn't direct any specific traffic back on port 80. It simply opens that port up to be forwarded from the internet as if you were to go in and put a manual port forward in.
The traffic coming back from port 49 may or may not use port 80. Most of the time with port triggering the traffic that comes in to the forwarding port (80) isn't sourced from the same port as the triggered port (49)
Lets say you have a PC on your lan with 192.168.1.10 and your router's ISP assigned WAN ip is 184.108.40.206. So you could have a connection being initiated outbound from 192.168.1.10 to 220.127.116.11:49 on the internet. Your router's triggering picks this up and opens 18.104.22.168:80 -> 192.168.1.10:80
The traffic *could* come back from 22.214.171.124 to --> 126.96.36.199:80 but it doesn't have to.
The source IP *could* also be 188.8.131.52:49 but most of the time it isn't.
So let's say you need a server at 184.108.40.206 to be able to get back to you on 220.127.116.11:80. However, you can't keep port 80 forwarded all the time for security reasons. Well you know that whenever your PCs go outbound to destination port 49 that's a legit reason tp let someone in on port 80. Hence, a good case for port triggering.
I am still not understanding where you are coming from but let me type from the book and you might get a understanding of what I am talking about here.
My point is that there is no correlation or direct tie back that port 49 is coming back on port 80.
It *can* but it isn't forced to and doesn't have to.
It saids in the book Port triggering opens a port when a pc on the network initiate communication through another port. For example, in figure 9-37b, computer C sends data to port 50 to a computer on the internet. The router is configured to open port 80 for communication from this remote computer. Port 80 is closed until this trigger occurs.
Yes that statement is true BUT that doesn't mean that the return traffic will come from port 50. It will just come from the internet computer's IP address. Most likely sourced from a NAT port.
That also doesn't restrict the port forward on 80 to *only* allow computer C to send traffic back. In that time span where the port trigger is opened it is quite possible and likely that any computer can come back on 80.
I meant *internet computer, not computer C
That also doesn't restrict the port forward on 80 to *only* allow that specific internet computer to send traffic back. In that time span where the port trigger is opened it is quite possible and likely that any computer can come back on 80.
It's very important to know that the original communication from your local PC behind the router to the internet computer on port 50 isn't being "forced over" or "carried over" to port 80 on your router.
So basically it is going to open the port for communication right.
Just in general. Yes.
Just like if you go in and put in the port forward manually.
No special carry-over or transition from the original outgoing connection to port 50. That port 50 trigger is only there so the router knows WHEN to open port 80 up for forwarding not WHAT to move over to port 80.
Do you mean to forward data request to port 80 right.
When it opens port 80 up it just listens for any traffic destined for it's WAN ip on port 80 and then forwards it to the local PC.
Are you talking about on the port triggering
Same for port triggering and standard port forwarding
Only difference is that your outbound connection to port 50 is what sets it up instead of you doing it manually.
Thank you for your help Josh and I will ask more question If I have any. Thanks for your time.
No prob. Feel free to rate my service :D