NAME
nemesis-ethernet − Ethernet Protocol (The Nemesis Project)
SYNOPSIS
nemesis-ethernet [-vZ?] [-d Ethernet-device ] [-H source-MAC-address ] [-M destination-MAC-address ] [-P payload-file ] [-T Ethernet-type ]
DESCRIPTION
The Nemesis Project is 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-ethernet provides an interface to craft and inject Ethernet frames allowing the user to inject an entirely arbitrary Ethernet frame.
ETHERNET OPTIONS
-d Ethernet-device
Specify the name (for UNIX-like systems) or the number (for Windows systems) of the Ethernet-device to use (eg. fxp0, eth0, hme0, 1).
-H source-MAC-address
Specify the source-MAC-address (XX:XX:XX:XX:XX:XX).
-M destination-MAC-address
Specify the destintion-MAC-address (XX:XX:XX:XX:XX:XX).
-P payload-file
This will cause nemesis-ethernet to use the specified payload-file as the payload when injecting Ethernet frames. The maximum payload size is 1500 bytes in order to account for the maximum Ethernet frame size. Payloads can also be read from stdin by specifying ’-P -’ instead of a payload-file.
The payload file can consist of any arbitary data though it will be most useful to create a payload resembling the structure of a packet type not supported by nemesis. Used in this manner, virtually any link layer frame can be injected.
-T Ethernet-type
Specify the Ethernet-type as an integer. Valid Ethernet types include:
512 (PUP)
2048 (IP)
2054 (ARP)
32821 (RARP)
33024 (802.1q)
34525 (IPv6)
34915 (PPPOE discovery)
34916 (PPPOE session)
-v verbose-mode
Display the injected packet in human readable form. Use twice to see a hexdump of the injected packet.
-Z list-network-interfaces
Lists the available network interfaces by number for use in link-layer injection.
NOTE: This feature is only relevant to Windows systems.
DIAGNOSTICS
Nemesis-ethernet returns 0 on a successful exit, 1 if it exits on an error.
BUGS
Send concise and clearly written bug reports to jeff [AT] snort.org
AUTHOR
Jeff Nathan <jeff [AT] snort.org>
SEE ALSO
nemesis-arp(1), nemesis-dns(1), nemesis-icmp(1), nemesis-igmp(1), nemesis-ip(1), nemesis-ospf(1), nemesis-rip(1), nemesis-tcp(1),