DEVICE PARAMETERS: <type of
DEVICE PARAMETERS: <type of
DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.
> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of
DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.
. New line terminates the list of names.
> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of
DEVICE PARAMETERS: <type of
DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.
> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of
DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.
. New line terminates the list of names.
. New line terminates the list of names.
tcp "client:www.mail.ru:80"
NEWLINEIS
Sets the string which must replace any original LF symbol while working with strings. See "
samples/strings.fws"
'\r\n'
data
"GET / HTTP/1.1
User-Agent: Opera/9.00 (Windows NT 5.1; U; en)
Host: www.mail.ru
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command
FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command
FASTTEST PARAMETERS: no parameters
and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
Enables
FASTTEST PARAMETERS: no parameters
regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
".
or option -c). In common regime it may be among parameters to command only.
-Language: ru_RU,ru;q=0.9,en;q=0.8
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command
FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command
FASTTEST PARAMETERS: no parameters
and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of
SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).
ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
or option -c). In common regime it may be among parameters to command only.
. It may be processed as command while testing packet filter only (command
FASTTEST PARAMETERS: no parameters
Enables
FASTTEST PARAMETERS: no parameters
regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "
samples/FASTTEST PARAMETERS: no parameters
".
".
or option -c). In common regime it may be among parameters to command only.
-Charset: iso-8859-1
RANGE PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given
RANGE PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given
RANGE PARAMETERS: <number of start packet> <number of stop packet>
While imitation of application's work the work will be performed with packets (from trace file) which are within the given range. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.
. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.
. Null value for start packet means first packet in file. Null value for stop packet means last packet in file.
: bytes=45-46
Connection: Keep-Alive
"