string currentNumberOfMessages = '0'
.nummes ''
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
PARAMETERS: <number of iterations>
Command instructs that next
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) or next block of script will be processed by several times = <number of iterations>. The "inf" value is available which means infinite iterant processing.
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
"new connection...\n"
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
"client:pop3.mail.ru:110#session"
RECV
Analog of
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command. This command is more convenient to use when working with tcp(udp). It clears the mask of packet automatically so stops working after receiving any data. It also enables mode when received packet is copied to the buffer of current packet (
COPYREC PARAMETERS: no parameters
The received packet (see command
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command
PRECISEWAIT PARAMETERS: no parameters
After the work of WAIT command (its analogs) all trace threads will be blocked until the next call to WAIT command. So there will be no missed packets between subsequent calls to WAIT command.
). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of
COPYREC PARAMETERS: no parameters
The received packet (see command WAIT, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command PRECISEWAIT). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of COPYREC command.
command.
command.
command.
command).
IF PARAMETERS: <value1> <type of compare> <value2> "{" <first block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the first block of script if condition is met, otherwise processes the second block if it is specified. <Types of compare>: = (==), !=, >, <, >=, <=. Hexadecimals number are treated as strings (with 0x prefix). If you have problems try to watch how these values are represented by string using
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command for example.
'+OK\r\n'
{
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
"The server doesn't send invitation\n"
EXIT
Terminates the execution. The status may be some decimal number. Value 0 is reserved for successful test, 1 - fatal error, 2 - not successful test, 3 - error while TCP connecting or listening (timeout expires).
2
}
data 'user anettesttesting\r\n'
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).
Analog of
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command. This command is more convenient to use when working with tcp(udp). It clears the mask of packet automatically so stops working after receiving any data. It also enables mode when received packet is copied to the buffer of current packet (
COPYREC PARAMETERS: no parameters
The received packet (see command
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command
PRECISEWAIT PARAMETERS: no parameters
After the work of WAIT command (its analogs) all trace threads will be blocked until the next call to WAIT command. So there will be no missed packets between subsequent calls to WAIT command.
). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of
COPYREC PARAMETERS: no parameters
The received packet (see command WAIT, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command PRECISEWAIT). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of COPYREC command.
command.
command.
command.
command).
IF PARAMETERS: <value1> <type of compare> <value2> "{" <first block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the first block of script if condition is met, otherwise processes the second block if it is specified. <Types of compare>: = (==), !=, >, <, >=, <=. Hexadecimals number are treated as strings (with 0x prefix). If you have problems try to watch how these values are represented by string using
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command for example.
'+OK\r\n'
{
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
"User name is not accepted\n"
EXIT
Terminates the execution. The status may be some decimal number. Value 0 is reserved for successful test, 1 - fatal error, 2 - not successful test, 3 - error while TCP connecting or listening (timeout expires).
2
}
data '
PASS PARAMETERS: <number of bytes>
Increases the byte pointer for the given <number of bytes>.
anettest\r\n'
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).
Analog of
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command. This command is more convenient to use when working with tcp(udp). It clears the mask of packet automatically so stops working after receiving any data. It also enables mode when received packet is copied to the buffer of current packet (
COPYREC PARAMETERS: no parameters
The received packet (see command
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command
PRECISEWAIT PARAMETERS: no parameters
After the work of WAIT command (its analogs) all trace threads will be blocked until the next call to WAIT command. So there will be no missed packets between subsequent calls to WAIT command.
). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of
COPYREC PARAMETERS: no parameters
The received packet (see command WAIT, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command PRECISEWAIT). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of COPYREC command.
command.
command.
command.
command).
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to GOTO command but performs back search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
command but performs
BACK PARAMETERS: <number of bytes>
Reduces the pointer for the given <number of bytes>.
search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
'+OK'
)
IF PARAMETERS: <value1> <type of compare> <value2> "{" <first block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the first block of script if condition is met, otherwise processes the second block if it is specified. <Types of compare>: = (==), !=, >, <, >=, <=. Hexadecimals number are treated as strings (with 0x prefix). If you have problems try to watch how these values are represented by string using
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command for example.
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to GOTO command but performs back search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
command but performs
BACK PARAMETERS: <number of bytes>
Reduces the pointer for the given <number of bytes>.
search.
command. 1 - successful search, 0 - not successful search.
= 0 {
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
'received $data$'
EXIT
Terminates the execution. The status may be some decimal number. Value 0 is reserved for successful test, 1 - fatal error, 2 - not successful test, 3 - error while TCP connecting or listening (timeout expires).
2
}
data 'stat\r\n'
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).
Analog of
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command
DEFAULTS PARAMETERS: {accept | drop | any |
REVERS
Request specification. May only be given in parameters for DEFAULTS command. Instructs to reverse the request for every packet.
}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND,
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.
). For TCP
DEVICE PARAMETERS: <type of device> {<name of interface>}
This command is deprecated. You should use
OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp (
doc/tcp_mode) this command will wait till connection with server is established or a client connection is accepted. For other types the command won't wait. See more in -d,-p,-T options.
and
CLOSE PARAMETERS: <interface's name>
Closes interface with given name.
commands.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.
the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD
Alias of
TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (
WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by
ADD command (or using of UNFIX command).
) then the command will ignore it and wait for a next packet (see also
SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sequence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.
).
command.
command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
command. This command is more convenient to use when working with tcp(udp). It clears the mask of packet automatically so stops working after receiving any data. It also enables mode when received packet is copied to the buffer of current packet (
COPYREC PARAMETERS: no parameters
The received packet (see command
WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above (
doc/packet_mask). The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULTS). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by
ADD command). If any of them is received then command terminates. Command waits packets until timeout expires (command
TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.
). See "
samples/waiting_packets.fws".
, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command
PRECISEWAIT PARAMETERS: no parameters
After the work of WAIT command (its analogs) all trace threads will be blocked until the next call to WAIT command. So there will be no missed packets between subsequent calls to WAIT command.
). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of
COPYREC PARAMETERS: no parameters
The received packet (see command WAIT, its analogs) will be copied to the buffer of current packet. Precision waiting must be first enabled (command PRECISEWAIT). See also
NOTCOPYREC PARAMETERS: no parameters
Reverses the action of COPYREC command.
command.
command.
command.
command).
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to GOTO command but performs back search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
command but performs
BACK PARAMETERS: <number of bytes>
Reduces the pointer for the given <number of bytes>.
search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
'+OK'
)
IF PARAMETERS: <value1> <type of compare> <value2> "{" <first block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the first block of script if condition is met, otherwise processes the second block if it is specified. <Types of compare>: = (==), !=, >, <, >=, <=. Hexadecimals number are treated as strings (with 0x prefix). If you have problems try to watch how these values are represented by string using
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command for example.
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to GOTO command but performs back search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
command but performs
BACK PARAMETERS: <number of bytes>
Reduces the pointer for the given <number of bytes>.
search.
command. 1 - successful search, 0 - not successful search.
= 0 {
PRINTL
Analog of
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command. Additionally performs the line feed.
'received wrong $data$'
EXIT
Terminates the execution. The status may be some decimal number. Value 0 is reserved for successful test, 1 - fatal error, 2 - not successful test, 3 - error while TCP connecting or listening (timeout expires).
2
}
PASS PARAMETERS: <number of bytes>
Increases the byte pointer for the given <number of bytes>.
This special value allows to get the current value of byte pointer.
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to GOTO command but performs back search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
or
GOTOB PARAMETERS: <value of any type> [<stop position>]
Is similar to
GOTO PARAMETERS: <value of any type> [<stop position>]
Performs the search of the given value in current packet. The search will be started from the current position of byte pointer. Value may have any type. The result of search is available through
GOTORES
This is a special value which allows to get the result of last search performed by GOTO or GOTOB command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
command but performs
BACK PARAMETERS: <number of bytes>
Reduces the pointer for the given <number of bytes>.
search.
command. 1 - successful search, 0 - not successful search.
keyword. In the case of successful search the byte pointer will be moved to the found entry. Stop position may be equal to -1. It means search to the end of packet. Stop position may be omitted but in this case parameters must be enclosed in brackets.
' '
)
int end = CURPOS
This special value allows to get the current value of byte pointer.
end -= start
SETPOS PARAMETERS: <field's name> <decimal value of a new position>
Sets a new position for the given field.
PARAMETERS: <name of field> <decimal value of a new size of field>
Sets size of field. Value "any" may be used to specify undefined size. That means that field will expand till the end of packet. Only fields with string type have undefined size initially. Undefined size may be also set for any hex field. A variable may be given so the size may be calculated before. See "
samples/http_parser".
Analog of
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command. Additionally performs the line feed.
'nummes = $nummes$'
IF PARAMETERS: <value1> <type of compare> <value2> "{" <first block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the first block of script if condition is met, otherwise processes the second block if it is specified. <Types of compare>: = (==), !=, >, <, >=, <=. Hexadecimals number are treated as strings (with 0x prefix). If you have problems try to watch how these values are represented by string using
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command for example.
PARAMETERS: <name of wav file>
Windows only. Plays the specified sound, WAV-file. Sound system must be enabled. If the file is not found then default Windows sound will be played. If the file is in current folder or in standard system folder then the full path is not required (Media/<name>).
Under UNIX the sound will be played by PC speaker.
'Media/Windows Exclamation.wav'
PRINTL
Analog of
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command. Additionally performs the line feed.
'NEW MESSAGES'
}
currentNumberOfMessages = nummes
data "quit\r\n"
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).
PARAMETERS: <interface's name>
Closes interface with given name.
Analog of
PRINT
Displays the given message. Use symbol
in message to indicate that line feed must be performed.
command. Additionally performs the line feed.
"wait before next connection"
PAUSE PARAMETERS: <number of milliseconds>
Pauses the execution for a specified interval of time.