Stonesoft stonegate 5.2, Руководство по установке

Страница: 42 / 109

42
Chapter 5 Defining Sensors and Analyzers
6. Click OK .
Repeat these steps to define any additional capture interfaces.
Defining Inline Interfaces
The number of inline interfaces you can have are limited by the license in use. One inline
interface always comprises two physical interfaces, as the traffic is forwarded from one interface
to the other. The allowed traffic passes through as if it was going through a network cable. The
traffic you want to stop is dropped by the Sensor.
Inline interfaces (like capture interfaces) are associated with a Logical Interface, which is used
in the IPS policies and the traffic inspection process to represent one or more Sensor
interfaces.
Fail-open network cards have fixed pairs of ports. Take particular care to map these ports
correctly during the initial configuration of the engine. Otherwise, the network cards do not
correctly fail open when the sensor is offline. If you use the automatic USB memory stick
configuration method for the engine’s initial configuration, the ports are configured
automatically. See
Configuring the Engine Automatically with a USB Stick (page 64) for more
information.

To define an inline interface
1. Right-click and select New Physical Interface . The Physical Interface Properties dialog
opens.
2. Select the Interface ID .
What’s Next?
 To define inline interfaces, proceed to Defining Inline Interfaces (page 42).
 To define how an inline sensor handles traffic when the traffic load is too high, proceed
to
Bypassing Traffic on Overload (page 43).
 Otherwise, proceed to Finishing the Engine Configuration (page 44).