Copyright © 2016 Frontier Communications. All Rights Reserved.
For example, a gaming server is accessed using UDP protocol on port
2222. The gaming server then responds by connecting the user using
UDP on port 3333, when a gaming session is initiated.
In this case, port triggering must be used since it conflicts with the
following default firewall settings:
• Firewall blocks inbound traffic by default.
• Server replies to your Gateway IP, and the connection is not sent back
to the host since it is not part of a session.
PORT TRIGGERING AND REMOTE
ADMINISTRATION
To resolve the conflict, a port triggering entry must be defined, which
allows inbound traffic on UDP port 3333 only after a network host
generated traffic to UDP port 2222. This results in your Gateway
accepting the inbound traffic from the gaming server and sending it
back to the network host which originated the outgoing traffic to UDP
port 2222.
To configure port triggering:
1. Select Port Triggering.