Specifications

Issue 1.0, April 2006 Section 364-180-N02



Configuring triggers

A trigger allows an application to open a secondary port in order to transport packets. The most

common applications that require secondary ports are FTP and NetMeeting. This section assumes

that you have followed the instructions in Enabling Security.

To configure a trigger:

1. Go to the Policies, Triggers and Intrusion Detection section of the Security Interface

Configuration. Click on Firewall Trigger Configuration. The “Firewall Trigger Configuration”

page is displayed. There are no triggers defined at this time. Click on the

New Trigger link. The following page is displayed:

Figure 6-55 Web Tool – Security: Firewall Add Trigger page

2. Configure the trigger as follows:

Transport Type; select a transport type from the drop-down list, depending on whether you are

adding a trigger for a TCP or a UDP application.

Port Number Start; type the start of the trigger port range that the primary session uses.

Port Number End; type the end of the trigger port range that the primary session uses.

Allow Multiple Hosts; select allow if you want a secondary session to be initiated to/from

different remote hosts. Select block if you want a secondary session to be initiated only to/from

the same remote host.

Max Activity Interval; type the maximum interval time (in milliseconds) between the uses of

secondary port sessions.

Enable Session Chaining; select Allow or Block depending on whether you want to allow

multi-level TCP session chaining.

Enable UDP Session Chaining; select Allow or Block depending on whether you want to allow

The availability of features and technical specifications herein subject to change without notice.