Sniffer is a C program that parses and interprets captured Ethernet traffic containing IP datagrams (UDP/TCP), and stores the captured payloads, email messages and HTTP cookies sent into files.
Supply any pcap file, produced by tcpdump, that contains a packet trace for the program to use as input: ./selected_parser [pcap_file]
Parses each packet in the file provided on standard input and displays basic header information on standard output:
- Packet type (TCP, UDP, other)
- Source and destination MAC address
- Source and destination IP address (if IP packet)
- Source and destination ports (if TCP or UDP)
- Checksum (if TCP) and payload size
Prints the total number of packets processed and the numbers of TCP, UDP and non-TCP/UDP packets.
Program records each TCP connection into into files that represent the data sent and received on each side of the connection.
For each connection, we create three files in the current directory:
- Metadata (e.g., “1.meta”): basic information about the connection, including:
- Initiator and responder IP address
- Initiator and responder port number
- Number of packets sent, in each direction
- Number of bytes sent, in each direction
- Number of duplicate packets detected, in each direction
- Whether the connection was closed before EOF was reached (4-way handshake)
- Data from initiator (e.g., “1.initiator”): all the TCP payload data in the connection sent from the initiator to the responder, but only if the responder has acknowledged it and it is not a duplicate. Data in each subsequent packet in the connection is concatenated to the end of the file as it is acknowledged.
- Data from responder (e.g., “1.responder”): all corresponding data sent from responder to initiator.
Records the SMTP email traffic in the packet trace via TCP servers. For each email message sent to an SMTP server, it creates a file (e.g., “1.mail”) that contains:
- The IP addresses of the sender and receiver
- Whether the message was accepted or rejected by the server
- The message headers and body (if any)
Detects and parses cookies in HTTP traffic. Stores all the name/value pairs in one file for each connection (e.g., “1.cookie”)