// Sample file for progam AnetTest.
// run program as
//   anettest -d eth0 -f generate_tcp_packet.fws
// to generate this packet (instead of 
'eth0'
 you may insert your adapter's name, may be IP address)

INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without INCLUDE
   
PARAMETERS: <name of file>
Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined. You can also type just the name of file without include before it.

 before it.

 before it.

 tcp.fws   
// file from HEADERS folder, containing default values for fields

srcip 1.1.1.1
dstip 192.168.0.1

srcport  = 45000
dstport  = 80

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

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

".

".

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

  
// sending packet