Get raw text for this example (you can click any command below to see its doc) 
/*
    Set of examples about using strings.
    run:
       anettest -d eth0 -f this_file.fws
 */


INCLUDE
   
PARAMETERS: <name of file>


Starts processing the content of given file. The search of file will be performed in the current directory, all search paths (see option -I). For every path the content of samples, headers, traces folders will be also examined.




 tcp


// symbol \ before a new line causes that the new line will be ignored


// otherwise LF symbol will be inserted


td = "\
FIRST
   
PARAMETERS: no command


This special value retrieves field's value from the first packet in trace file.




   
PARAMETERS: no command


This special value retrieves field's value from the first packet in trace file.




 line
SECOND
   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




 line
"

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




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







// CRLF symbol may be implemented by adding \r sequence


td = "\
FIRST
   
PARAMETERS: no command


This special value retrieves field's value from the first packet in trace file.




   
PARAMETERS: no command


This special value retrieves field's value from the first packet in trace file.




 line\r
SECOND
   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




 line"

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




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






NEWLINEIS
   
PARAMETERS: <string>


Sets the string which must replace any original LF symbol while working with strings. See "samples/strings.fws"




 
"\r\n"
  
// indicates to replace a new line by the specified sequence


td =
"first line
SECOND
   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




   
PARAMETERS: no command


This special value retrieves field's value from the second packet in trace file.




 line
"

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




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