/*
Transmit packets from one interface to another (and will change their content if you uncomment some lines).
Parameter 'sourceIP' may be defined prior to processing of this file if you want to set filter on source IP.
Run like this:
anettest -d eth0#0 -d eth1#1 -f this_file.fws
anettest -d eth0#0 -d eth1#1 define sourceIP 1.1.1.1 this_file.fws
*/

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.

tcp
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.

udp

PRECISEWAIT PARAMETERS: no parameters
After the work of WAIT command (its analogs) all trace threads will be blocked until the next call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT 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 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. So there will be no missed packets between subsequent calls to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

(command DEFAULT). For TCP 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.

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 PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

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" sentence. 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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). 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.

// causes that no packets will be missed, all packets will be transmitted even under short-term high load
COPYREC PARAMETERS: no parameters
The received packet (see command WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). 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 PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command.

). See also NOTCOPYREC PARAMETERS: no parameters
Reverses the action of COPYREC PARAMETERS: no parameters
The received packet (see command WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

). 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.

// causes that recieved packet will be copied to buffer of generated packet

IFDEF PARAMETERS: <name of entity> "{" <script's block> "}"
Executes block if given entity has been defined (entity: variable, field, someone defined by GDEF PARAMETERS: <new name> <original name>
Defines the substitution which will be applied while reading almost any read word from text. <New name> will be replaced by <original name>. This substitution may be also performed in strings enclosed in apostrophes. In this case the name must be enclosed in $ (ex: 'value = $name$').

or DEFINE PARAMETERS: <name> <value>
Defines the substitution which will be applied while reading some values (in parameters to commands and others). <name> will be replaced by <value>. This substitution may be also performed in strings enclosed in apostrophes. In this case the <name> must be enclosed in $ (ex: 'value = $name$'. See also command GDEF PARAMETERS: <new name> <original name>
Defines the substitution which will be applied while reading almost any read word from text. <New name> will be replaced by <original name>. This substitution may be also performed in strings enclosed in apostrophes. In this case the name must be enclosed in $ (ex: 'value = $name$').

commands).

sourceIP {
PRINTL PARAMETERS: <message>
Analog of PRINT PARAMETERS: <message>
Displays the given message. Use symbol
in message to indicate that line feed must be performed.

command. Additionally performs the line feed.

'filter is set: only packets from $sourceIP$ are transmitted'
FILTER PARAMETERS: <name of interface> <filter string>
Sets the fast low-level filter (which is used by tcpdump) for the given interface. The format of filter is described in libpcap (WinPcap) or tcpdump documentation. See "samples/my_gateway"

1 'src $sourceIP$'
// sets fast low-level libpcap filter for interface 1
}

QUIET PARAMETERS: no parameters
Instructs to not display some annoying messages.

// avoids some annoying messages

// ADDING EXPECTED PACKETS

MI PARAMETERS: <name of interface>
Sets the main interface at which packets will be generated or waited (by default it's the first opened interface). The unique name of interface must be specified which may be defined while opening (-d option or OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp 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.

command) after symbol # (e.g. "-d eth0#0"). If no unique name is specified then it will be assigned to number 0,1,2,3,... Default requests are being overwritten: a single 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
Enables fasttest regime for packet filter test. See "samples/fasttest".

or option -c). In common regime it may be among parameters to command only.

request is set for the new main interface, others are ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. 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).

ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND ANY. 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".

or option -c). In common regime it may be amoung parameters to command only. This special word may also be used as value for field that means exclusion the all conditions with this field from current mask of packet - value of the field may be any.

. 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
Enables fasttest regime for packet filter test. See "samples/fasttest".

. This means that further WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (its analogs) will wait packet ONLY at the new main interface. In order to wait a packet at several interfaces use command DEFAULTS PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT 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 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).

, WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

and its analogs). Initially default requests are 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.

ANY ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND ANY. 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".

... i.e. a single request for the first interface specified via option -d.

after command MI PARAMETERS: <name of interface>
Sets the main interface at which packets will be generated or waited (by default it's the first opened interface). The unique name of interface must be specified which may be defined while opening (-d option or OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp 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.

request is set for the new main interface, others are ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND ANY. 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".

. This means that further WAIT command (its analogs) will wait packet ONLY at the new main interface. In order to wait a packet at several interfaces use command DEFAULTS PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT 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 and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.

command) after symbol # (e.g. "-d eth0#0"). If no unique name is specified then it will be assigned to number 0,1,2,3,... Default requests are being overwritten: a single ACCEPT request is set for the new main interface, others are ANY. This means that further WAIT command (its analogs) will wait packet ONLY at the new main interface. In order to wait a packet at several interfaces use command DEFAULTS after command MI or explicitly specify requests after WAIT command.

or explicitly specify requests after WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command.

or explicitly specify requests after WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command.

1 // sets 0 as interface from which packets will be received

// description of expected tcp packets

NAME PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

"tcp"

CLEARMASK PARAMETERS: no parameters
The mask of packet (the set of previously defined conditions) will be cleared. New mask will correspond to any packet. This command is usually contained in headers to make the mask correspond to all packets of given type (ex: TCP packets).

// empties mask i.e. any tcp packet to wait so far (not considering low-level filter)
ethproto = ip
ip.proto = tcp
// dstport = 45

// messages which will be displayed on recieving tcp packet

MES PARAMETERS: <string of message>
Defines the message which will be displayed the every time on receiving the currently described packet. Substitutions are allowed in the form of $name$. The 'name' may reference to the field's name, variable's name, someone defined by GDEF PARAMETERS: <new name> <original name>
Defines the substitution which will be applied while reading almost any read word from text. <New name> will be replaced by <original name>. This substitution may be also performed in strings enclosed in apostrophes. In this case the name must be enclosed in $ (ex: 'value = $name$').

command. In the case of field's name field's value will be retrieved from the content of received packet.

"$srcip$ << $syn$ : $fin$ : $ack$ :\t$ip.len$ :\t$num$\n"

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 PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

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 PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command (or using of UNFIX PARAMETERS: no parameters
By default after the work of WAIT command (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAIT. This command marks these old packets as newly added. The previous status for them will be lost. Take a note of that ALL old packets will be unfixed, so they will be waited: this may cause unexpected results. Consider the use of CLEARREG PARAMETERS: no parameters
Clears the information about all the packets which were added to the waited ones (by WAIT, ADD PARAMETERS:
Alias of TOWAIT command.

commands). They will not be displayed in final report (or in the report that is displayed by SHOWREP PARAMETERS: no parameters
Displays a report which is the same as that displayed while program termination.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

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).

but before 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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

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 (or using of UNFIX PARAMETERS: no parameters
By default after the work of WAIT command (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

. This command marks these old packets as newly added. The previous status for them will be lost. Take a note of that ALL old packets will be unfixed, so they will be waited: this may cause unexpected results. Consider the use of CLEARREG PARAMETERS: no parameters
Clears the information about all the packets which were added to the waited ones (by WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "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".

WAITALL" sentence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command 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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

stop waiting if it was accepted after 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
Enables fasttest regime for packet filter test. See "samples/fasttest".

but before WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

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.

// adds the described tcp packet to expected ones

// description of expected udp packets

NAME PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

"udp"

// any udp packet
CLEARMASK PARAMETERS: no parameters
The mask of packet (the set of previously defined conditions) will be cleared. New mask will correspond to any packet. This command is usually contained in headers to make the mask correspond to all packets of given type (ex: TCP packets).

ethproto = ip
ip.proto = udp

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

command (or using of UNFIX command).

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 (or using of UNFIX PARAMETERS: no parameters
By default after the work of WAIT command (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

command (or using of UNFIX command).

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

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.

// adds the described packet udp to expected ones

. 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".

or option -c). In common regime it may be among parameters to command only.

). See "samples/waiting_packets.fws".

}
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 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).

). See "samples/waiting_packets.fws".

... i.e. a single request for the first interface specified via option -d.

}
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 and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.

). See "samples/waiting_packets.fws".

command.

or explicitly specify requests after WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command.

0 // sets 0 as interface from which packets will be send

// infinite cycle

CYC PARAMETERS: <number of iterations>
Command instructs that next WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). 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.

inf {

// WAITS AN EXPECTED PACKET

WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

command (or using of UNFIX command).

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 (or using of UNFIX PARAMETERS: no parameters
By default after the work of WAIT command (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

// SENDING RECIEVED PACKET FROM ANOTHER INTERFACE

IFR PARAMETERS: <name of packet or status of last wait operation> "{" <block of script> "}" [ "else" "{" <second block of script> "}" ]
Processes the block of script if the last received packet (command WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

, its analogs) has the given name (which was specified by command NAME PARAMETERS: <name of packet>
Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."

). "timeout" may be specified as the name of packet what means that the block must be processed in the case of timeout. Command will not distinguish newly added packets and old ones if they have the same name. Take a note of it when using UNFIX PARAMETERS: no parameters
By default after the work of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT 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. 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 DEFAULT). 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.

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 PARAMETERS:
Alias of TOWAIT 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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command. See also CLEARREG PARAMETERS: no parameters
Clears the information about all the packets which were added to the waited ones (by WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

, ADD PARAMETERS:
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 PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

command (or using of UNFIX command).

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 this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.
For tcp (udp) this command is also used to check the general status of last waiting operation. Status string "error" may be given to check if connection is closed already. Check for timeout or error may be also performed just after opening of connection by command OPEN PARAMETERS: <interface's type> <interface's name>
Opens interface of given type. Types: eth, ip, tcp, udp. For tcp 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.

. See samples/tcp_gateway, samples/http_client, samples/http_server.

"tcp"
{ // if packet received this given name

//srcip 3.3.3.3 // changes only address of source
//ip.crc IPcrc // marks that crc must be recalculated
//tcp.crc TCPcrc // marks that crc must be recalculated

PRINT PARAMETERS: <message>
Displays the given message. Use symbol
in message to indicate that line feed must be performed.

"send tcp\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
Enables fasttest regime for packet filter test. See "samples/fasttest".

regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

// generates packet
}

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

}
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. 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 DEFAULT). 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.

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 PARAMETERS:
Alias of TOWAIT 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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

command (or using of UNFIX command).

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 this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

. See samples/tcp_gateway, samples/http_client, samples/http_server.

"udp" {

//srcip 3.3.3.3 // changes only address of source
//ip.crc IPcrc // marks that crc must be recalculated
//udp.crc UDPcrc // marks that crc must be recalculated

PRINT PARAMETERS: <message>
Displays the given message. Use symbol
in message to indicate that line feed must be performed.

"send udp\n"

// generates packet
}

UNFIX PARAMETERS: no parameters
By default after the work of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

. This command marks these old packets as newly added. The previous status for them will be lost. Take a note of that ALL old packets will be unfixed, so they will be waited: this may cause unexpected results. Consider the use of CLEARREG PARAMETERS: no parameters
Clears the information about all the packets which were added to the waited ones (by WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

). 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.

command (or using of UNFIX command).

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. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. 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 DEFAULT). 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 PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
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 PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

command). If this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. 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 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".

command (or using of UNFIX command).

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 this command is typed at the end of script then it omits the displaying of final report (sense there are no packet in it).

command.

// forget that an expected packet's been received so it will be able to be received again
}