INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without
INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without
INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without include before it.
before it.
before it.
udp
udp.data 'hello'
srcip = 1.1.1.1
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 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
".
".
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).
dstip 2.2.2.2
//dstip www.google.com
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 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
".
".
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).
srcport 10000
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 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
".
".
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).
REP PARAMETERS: <the number of generation>
The next generation command (command
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).
) will generate not one, but several packets.
The use of this command also affects the request for packet: the packet must be accepted the specified number of times.
10
dstport 80
srcport 10001
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 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
".
".
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).
REP PARAMETERS: <the number of generation>
The next generation command (command
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).
) will generate not one, but several packets.
The use of this command also affects the request for packet: the packet must be accepted the specified number of times.
= 3
INTERVAL PARAMETERS: <number of milliseconds>
Sets the value of interval between generating multiple packets while using command
REP PARAMETERS: <the number of generation>
The next generation command (command
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).
) will generate not one, but several packets.
The use of this command also affects the request for packet: the packet must be accepted the specified number of times.
.
1000
udp.data 'hol'
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 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
".
".
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).
INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without
INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without
INCLUDE PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without include before it.
before it.
before it.
tcp
srcport 10000
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 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
".
".
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).
dstport 80
srcport 10001
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 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
".
".
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).
PAUSE PARAMETERS: <number of milliseconds>
Pauses the execution for a specified interval of time.
1000
tcp.data 'hol'
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 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
".
".
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).