When using classic port forwarding you've got one specific issue: You've got a 1:1 relation between the incoming port and the LAN member this is forwarded to.
For example, you can specify that incoming traffic on port 12345 (bad idea; never use that port!) to the machine 192.168.2.2. But if you, for example, play that game on more than one computer, you'd have to change the forward every time you switch machines.
Port triggering is an interesting approach to counter these disadvantages:
- The port is not necessarily open all the time (depends on whether your LAN IP changes).
- The port will always forward to the proper machine.
You'll still run into issues, if you want to use multiple machines at the same time, or you want to passively listen on ports (e.g. a web server), but that's something different.
So how does it work? Pretty easy.
Let's assume you'd like to play some game where you'd like to host single matches. If there's some authentication server your game will be connected to all the time, you can use the port that server is using as the trigger port. Let's assume it's port 5000.
To host games, other players have to be able to reach your PC on port 5001. So you create a new dynamic port activation with the following parameters:
- Triggering port: 5000
- Triggering protocol: (depends on the game, most likely TCP for non time sensitive stuff like authentication)
- Ports to be opened: 5001 to 5001 (typically UDP for most games)
And that's it.
Now, whenever you start the game and try to authenticate/login, the game will create an outgoing connection to its authentication server on port 5000.
The router will notice this, since it's the "trigger port", and enable/reroute port forwarding to the computer that made that connection.
The port forwarding is now active, you can play and host your matches, etc.
Also note that this feature isn't provided by all routers. Some use a different strategy to reroute ports in a changing environment. For example, AVM routers typically got an option to always assign port forwards to the same machine, even if its IP changes due to DHCP. While this is very convenient for things that work without outgoing connections (dedicated servers in general), it won't allow you to dynamically switch machines and use the same ports on them without reconfiguring port forwarding.
Specific information in your case can probably be found by clicking on the "What is that?" links. – user55325 – 2014-04-08T05:44:23.000
@user55325 Nope, the little what is there does not answer the question. – BadSnowflake – 2014-04-08T05:46:19.817
in that case, hopefully my answer is more helpful. :) – user55325 – 2014-04-08T05:49:32.013