Get raw text for this example (you can click any command below to see its doc)
/* Tcp server that accepts new connections, waits for predefined request and sends response. There is a sample of corresponding client. */QUIETTIMEOUTPARAMETERS: no parametersInstructs to not display some annoying messages.5000 OPENPARAMETERS: <interval in milliseconds>Defines the timeout for WAITcommand (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 WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.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: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.tcpPARAMETERS: <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.'s:localhost:67#s'TIMEOUT1000 CYCPARAMETERS: <interval in milliseconds>Defines the timeout for WAITcommand (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 WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.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: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.inf { NAMEPARAMETERS: <number of iterations>Command instructs that next WAITcommand (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.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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.4 dataPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."'2*2'// !!! will compare with the beginning of next received data (if at least one byte arrives)TOWAITNAMEPARAMETERS: {accept | drop | any }Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAITor 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 WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.(WAITALLPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.command).PARAMETERS: no parametersBy 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 CLEARREGPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks similar to "SENDWAITALL" sentence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".stop waiting if it was accepted after SENDPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.but before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/FASTTEST".PARAMETERS: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.9 dataPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."'3*3'TOWAITWAITALLPARAMETERS: {accept | drop | any }Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAITor 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 WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.(WAITALLPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.command).PARAMETERS: no parametersBy 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 CLEARREGPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks similar to "SENDWAITALL" sentence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".stop waiting if it was accepted after SENDPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.but before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/FASTTEST".PARAMETERS: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.IFRPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.command).PARAMETERS: no parametersBy 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 CLEARREGPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.error { BREAKPARAMETERS: <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, its analogs) has the given name (which was specified by command NAMEPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.). "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 UNFIXPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."command. See also CLEARREGPARAMETERS: no parametersBy default after the work of WAITcommand (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.. 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 CLEARREGPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.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. See samples/tcp_gateway, samples/http_client, samples/http_server.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.} IFRPARAMETERS: no parametersBreaks the cycle caused by using CYCcommand.PARAMETERS: <number of iterations>Command instructs that next WAITcommand (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.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.timeout { dataPARAMETERS: <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, its analogs) has the given name (which was specified by command NAMEPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.). "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 UNFIXPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."command. See also CLEARREGPARAMETERS: no parametersBy default after the work of WAITcommand (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.. 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 CLEARREGPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.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. See samples/tcp_gateway, samples/http_client, samples/http_server.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.'no answer'} else { IFR4 { dataPARAMETERS: <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, its analogs) has the given name (which was specified by command NAMEPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.). "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 UNFIXPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."command. See also CLEARREGPARAMETERS: no parametersBy default after the work of WAITcommand (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.. 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 CLEARREGPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.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. See samples/tcp_gateway, samples/http_client, samples/http_server.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.'4'} IFR9 { dataPARAMETERS: <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, its analogs) has the given name (which was specified by command NAMEPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.). "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 UNFIXPARAMETERS: <name of packet>Defines the name of currently described packet which will be displayed in report instead of not obvious "Packet on line ..."command. See also CLEARREGPARAMETERS: no parametersBy default after the work of WAITcommand (its analogs) the statuses for all waited packets will be fixed, so there may be no packets to wait for the next call to WAITPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.. 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 CLEARREGPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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). 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.command.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.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. See samples/tcp_gateway, samples/http_client, samples/http_server.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.'9'} PRINTLPARAMETERS: <message>Analog of PRINTcommand. Additionally performs the line feed.PARAMETERS: <message>Displays the given message. Use symbol in message to indicate that line feed must be performed.'server sent $data$'} SEND} CLOSEPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables FASTTESTregime for packet filter test. See "samples/FASTTESTPARAMETERS: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".".PARAMETERS: no parametersEnables fasttest regime for packet filter test. See "samples/FASTTEST".PARAMETERS: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".PARAMETERS: <interface's name>Closes interface with given name.'s'CLEARREGPARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDPARAMETERS: {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 DEVICEPARAMETERS: {accept | drop | any | REVERS}PARAMETERS: not commandRequest 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, WAITand its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADDPARAMETERS: <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.command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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.). See "samples/waiting_packets.fws".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 WAITcommand (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: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.commands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAITcommand.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(WAITALLPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe analog of WAITcommand. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADDPARAMETERS: {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 ADDcommand). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUTPARAMETERS:Alias of TOWAIT command.). See "samples/waiting_packets.fws".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.command (or using of UNFIXPARAMETERS:Alias of TOWAITcommand.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) then the command will ignore it and wait for a next packet (see also SENDWAITOTHERPARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT command.).PARAMETERS: no parametersWorks 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).PARAMETERS: no parametersBy 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 CLEARREGcommand.PARAMETERS: no parametersClears the information about all the packets which were added to the waited ones (by WAIT, ADDcommands). They will not be displayed in final report (or in the report that is displayed by SHOWREPPARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.).PARAMETERS: no parametersWorks 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 SENDbut before WAITALLPARAMETERS: {accept | drop | any }In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTESTand 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: no parametersEnables fasttest regime for packet filter test. See "samples/fasttest".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.PARAMETERS: no parametersThe 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 ADDcommand (or using of UNFIX command).PARAMETERS:Alias of TOWAIT 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).PARAMETERS: no parametersDisplays a report which is the same as that displayed while program termination.