Get raw text for this example (you can click any command below to see its doc)
/* Sends multiple packets changing the address of source program may be started as anettest -d eth0 -f this_file.fws */INCLUDEtcpPARAMETERS: <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 INCLUDEbefore it.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 INCLUDEbefore it.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.// standart templateREP1000PARAMETERS: <the number of generation>The next generation command (command SEND) will generate not one, but several packets.PARAMETERS: {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".The use of this command also affects the request for packet: the packet must be accepted the specified number of times.// generates no one packet, but 1000 packetsINCPARAMETERS:The field for which the value will be specified below becomes autoincremented. While generating several packets (command REP) the value of field will be incremented. See "samples/synflood.fws"PARAMETERS: <the number of generation>The next generation command (command SEND) will generate not one, but several packets.PARAMETERS: {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".The use of this command also affects the request for packet: the packet must be accepted the specified number of times.// value of field srcip will be incremented for every next packetsrcip 1.1.1.1// targetdstip 2.2.2.2 srcport 1 INCPARAMETERS:The field for which the value will be specified below becomes autoincremented. While generating several packets (command REP) the value of field will be incremented. See "samples/synflood.fws"PARAMETERS: <the number of generation>The next generation command (command SEND) will generate not one, but several packets.The use of this command also affects the request for packet: the packet must be accepted the specified number of times.// try to uncomment INCdstport 80 SENDcommand hear and dstport will be incrementedPARAMETERS:The field for which the value will be specified below becomes autoincremented. While generating several packets (command REP) the value of field will be incremented. See "samples/synflood.fws"PARAMETERS: <the number of generation>The next generation command (command SEND) will generate not one, but several packets.PARAMETERS: {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".The use of this command also affects the request for packet: the packet must be accepted the specified number of times.PARAMETERS: {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".