// Sample file for progam AnetTest.
// Run program as
// anettest -c trace1.pcap -c trace2.pcap -c trace3.pcap -f compare_mode1.fws

// You can also watch file "compare_mode.fws"

// Program will search all the packets defined below in trace-files.
// and will output info about packets for which search results don't correspond packet'
s requests (ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

or DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND DROP". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

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

)

// DEFINING DEFAULT REQUESTS (they will be applied if there are not enough requests for some packet)

DEFAULTS PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

, WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in DEFAULTS PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND, WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.

). See "samples/waiting_packets.fws".

and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.

(command DEFAULT). For TCP DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND but before WAITALL started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.

command.

command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (its analogs) will work differently: it will always wait for the whole timeout (not terminating on first received packet). So several packets may be registered as received. This command also defines the timeout for TCP server while waiting for connections.

). See "samples/waiting_packets.fws".

and its analogs). Initially default requests are ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

ANY ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND ANY. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

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

(command DEFAULT). For TCP DEVICE PARAMETERS: <type of DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of DEVICE PARAMETERS: <type of device> {<name of interface>}
Reopens interfaces. The type of device: eth, ip, tcp. The name of device is the same as for -d option, depends on the type of device. New line terminates the list of names.

. New line terminates the list of names.

the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

(WAITALL PARAMETERS: no parameters
The analog of WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
Alias of TOWAIT PARAMETERS: {accept | drop | any }
Analog of WAIT command. Adds the above packet to the set of packets which will be waited by command WAIT or its analogs. This command does not start actual waiting (doesn't suspend script execution). Nevertheless, just after adding the packet may be registered as received. If some packet is registered as received before the call to WAIT (WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

command.

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

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

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

command.

command).

) then the command will ignore it and wait for a next packet (see also SENDWAITOTHER PARAMETERS: no parameters
Works similar to "SEND WAITALL" sentence. Purpose: make atomic operation. Without this command there would be a chance that a waited packet did not cause command WAITALL stop waiting if it was accepted after SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

but before WAITALL PARAMETERS: no parameters
The analog of WAIT command. Doesn't add the previously defined packet to the list of waited ones. Starts waiting simply. Packets may be already added by ADD PARAMETERS:
Alias of TOWAIT command.

command (or using of UNFIX command).

started waiting. However it would be registered as received in any case. This command should be always used when you need to send a request and RELIABLY receive a response on it never missing.

command.

command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in DEFAULTS PARAMETERS: {accept | drop | any | REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

}
Defines default requests for packets. These requests will be applied when there are not enough explicitly defined requests for some packet (specified as parameters to command SEND, WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

and its analogs). Initially default requests are ACCEPT ANY ANY... i.e. a single request for the first interface specified via option -d.

command (or using of UNFIX command).

command.

command). If any of them is received then command terminates. Command waits packets until timeout expires (command TIMEOUT PARAMETERS: <interval in milliseconds>
Defines the timeout for WAIT command (and its analogs), also for imitation of application's work. Null value means infinite timeout (such timeout will not be applied for imitation of application's work). In the case of negative value its absolute value will be obtained as timeout, but WAIT PARAMETERS: {accept | drop | any }
Waits for packet whose mask is defined above. The command will finish work when such packet is received on waitable interface. The waitable interface is interface for which strict request (accept or drop) have been specified in parameters to command or in defaults (command DEFAULT). For TCP device the command will only wait data on the main interface. In the general case command may wait no one but several packets (added by ADD PARAMETERS:
Alias of TOWAIT command.

). See "samples/waiting_packets.fws".

and its analogs). Initially default requests are ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST and option -c) may simply separate packets one from another, so by this command the current content of buffer will be fixed and the new packet will be registered. The requests after command don't make sense in common regime (only while testing packet filter).

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

REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// REVERS PARAMETERS: not command
Request specification. May only be given in parameters for DEFAULT command. Instructs to reverse the request for every packet.

means reversing any explicit request specified for a packet

// PACKET'S MASK PARAMETERS: <field's mask>
Defines the mask for the next defined field. Mask is hexadecimal number. Value for field will be written only in bits corresponding not null bits of mask. See "headers/tcp_header.fws".

DEFINITIONS

// packet 1 - any packet with value of "srcip"
equal to 192.168.0.3

srcip 192.168.0.3 SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// for trace1: DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND DROP". It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

will be reversed to ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// for trace2: default request = ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

will be applied

// packet 2 - any packet with value of "srcip"
equal to 192.168.0.1

srcip 192.168.0.1 SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// for trace1 DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND DROP". It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// for trace2 default request = ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

will be applied

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

// resets packet's mask to 0, it will correspond to any packet
// otherwise the field "SRCIP"
will stay in mask, but we don't want it to apply for next packet

// another way to exclude the field from mask:
// srcip = any

// packet 3 - any packet with value of "srcport"
equal to 22

srcport 22 SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

ANY PARAMETERS: {accept | drop | any }
Request specification. No requests: the packet may be received or not. Analog of SEND ANY. It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be amoung parameters to command only. This special word may also be used as value for field that means exclusion the all conditions with this field from current mask of packet - value of the field may be any.

. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND DROP". It may be processed as command while testing packet filter only (command FASTTEST or option -c). In common regime it may be among parameters to command only.

". It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

ACCEPT PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must be received. Analog of SEND ACCEPT. It may be processed as command while testing packet filter only (command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

// for trace2 will be applied DROP PARAMETERS: {accept | drop | any }
Request specification. The request that the packet must not be received. May be used as command - replacement for "SEND PARAMETERS: {accept | drop | any }
In common regime generates the packet defined above. In other regimes (testing packet filter, see command FASTTEST PARAMETERS: no parameters
Enables fasttest regime for packet filter test. See "samples/fasttest".

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

request

/*
Result:
Packet on line 18 (compare_mode1.fws) : droped (dev 2)
Packet on line 23 (compare_mode1.fws) : droped (dev 1)
Packet on line 34 (compare_mode1.fws) : droped (dev 1)
*/