- Feb 21, 2013
- 3,591
- 2
- 679
- 265
I have a PC hosting mir3d behind a newly installed modem/router that doesn't have port forwarding in its setup webpage. Instead you are supposed to download mobile app, log into your ISP account and set it up from there. But I can't even log into that webpage to begin with, and tons of pple who managed to log in complain that it doesn't work...
So I looked seriously at port triggering, which is included in the local webpage modem setup, with the aim of actually using it.
I searched on the internet and found many places trying to explain what this port triggering is, but nobody actually explained the first thing what it is about, what it is and what it is not. Information on this subject is either incomplete, in that the explaining ends up to be about port forwarding only with a sideline mention of port triggering, or what is said about it is outright false or a nonsense, like that it is good for gaming.
To let the cat out of the bag, port triggering is NOT a replacement for port forwarding in any sense, whereby you open ports full time to allow WAN internet traffic into your LAN, like if you host mir server for pple to connect to it from remote places.
Port Triggering is meant to allow traffic from your LAN, via ports which are closed, to WAN. If it is a traffic to contact a website out there on the internet, the router will direct the returning replies (only) to the LAN computer that initially sent that traffic request to that website (ie, its LAN IP doesn't need to to be specified in the port triggering table, as it needs to be when you set up port forwarding).
As I understand it, outgoing ports on the router are normally, in its default setting, opened. It is only if you intentionally close the outgoing ports (for extra security reasons) that you then need to open the needed ones by using port triggering to open them on demand from within LAN.
By default, router comes with all incoming ports closed, except those which are commonly used, most common being port 80 for http protocol, or port 403 for https, more secure protocol that most websites these days will use.
Don't confuse this with windows firewall that resides on the PC, which by default keeps most outgoing ports closed (again, the most common one are left open). This is why programs when started for the first time pop up firewall message asking if you want to allow access to the LAN (and to internet) to open its firewall outgoing ports (the router ports will be opened by default, so once you allow it from your computer, it has internet access automatically (again assuming default router setting and the router is consumer variety).
So, the bottom line is, port triggering cannot be used to let the traffic from remote mir clients into your home network to connect to your mir server. It only works for the outbound traffic from your LAN, not for the incoming one, like the traffic you didn't request.
So I looked seriously at port triggering, which is included in the local webpage modem setup, with the aim of actually using it.
I searched on the internet and found many places trying to explain what this port triggering is, but nobody actually explained the first thing what it is about, what it is and what it is not. Information on this subject is either incomplete, in that the explaining ends up to be about port forwarding only with a sideline mention of port triggering, or what is said about it is outright false or a nonsense, like that it is good for gaming.
To let the cat out of the bag, port triggering is NOT a replacement for port forwarding in any sense, whereby you open ports full time to allow WAN internet traffic into your LAN, like if you host mir server for pple to connect to it from remote places.
Port Triggering is meant to allow traffic from your LAN, via ports which are closed, to WAN. If it is a traffic to contact a website out there on the internet, the router will direct the returning replies (only) to the LAN computer that initially sent that traffic request to that website (ie, its LAN IP doesn't need to to be specified in the port triggering table, as it needs to be when you set up port forwarding).
As I understand it, outgoing ports on the router are normally, in its default setting, opened. It is only if you intentionally close the outgoing ports (for extra security reasons) that you then need to open the needed ones by using port triggering to open them on demand from within LAN.
By default, router comes with all incoming ports closed, except those which are commonly used, most common being port 80 for http protocol, or port 403 for https, more secure protocol that most websites these days will use.
Don't confuse this with windows firewall that resides on the PC, which by default keeps most outgoing ports closed (again, the most common one are left open). This is why programs when started for the first time pop up firewall message asking if you want to allow access to the LAN (and to internet) to open its firewall outgoing ports (the router ports will be opened by default, so once you allow it from your computer, it has internet access automatically (again assuming default router setting and the router is consumer variety).
So, the bottom line is, port triggering cannot be used to let the traffic from remote mir clients into your home network to connect to your mir server. It only works for the outbound traffic from your LAN, not for the incoming one, like the traffic you didn't request.
Last edited:
