|nemesis-tcp(1)||General Commands Manual (usm)||nemesis-tcp(1)|
nemesisis designed to be a command line-based, portable human IP stack for UNIX-like and Windows systems. The suite is broken down by protocol, and should allow for useful scripting of injected packets from simple shell scripts.
nemesis-tcpprovides an interface to craft and inject TCP packets allowing the user to specify any portion of a TCP packet as well as lower-level IP packet information.
’. If flags are specified in the form ‘
’ then the TCP header will be built without flags.
nemesis-tcpto use the specified TCP options file as the options when building the TCP header for the injected packet. TCP options can be up to 40 bytes in length. The TCP options file must be created manually based upon the desired options. TCP options can also be read from stdin by specifying ‘
nemesis-tcpto use the specified payload file as the payload when injecting TCP packets. For packets injected using the raw interface (where
-dis not used), the maximum payload size is 65415 bytes. For packets injected using the link layer interface (where
-dIS used), the maximum payload size is 1380 bytes. Payloads can also be read from stdin by specifying ‘
’ instead. Windows systems are limited to a maximum payload size of 1380 bytes for TCP packets.
-Fcommand line switch by separating the options with commas (eg.
-FD,M) or spaces (eg.
-FM223). The IP fragmentation offset is a 13-bit field with valid values from 0 to 8189. Don't fragment (DF), more fragments (MF) and the reserved flag (RESERVED or RB) are 1-bit fields. NOTE: Under normal conditions, the reserved flag is unset.
nemesis-tcpto use the specified IP options file as the options when building the IP header for the injected packet. IP options can be up to 40 bytes in length. The IP options file must be created manually based upon the desired options. IP options can also be read from stdin by specifying
nemesis-tcpreturns 0 on a successful exit, 1 if it exits on an error. nemesis-arp(1), nemesis-dhcp(1), nemesis-dns(1), nemesis-ethernet(1), nemesis-icmp(1), nemesis-igmp(1), nemesis-ip(1), nemesis-ospf(1), nemesis-rip(1), nemesis-udp(1). Mark Grimes <email@example.com> and
|December 16, 2019|