Network Packet Forensic using Wireshark
Today we are going to discuss “TCP Forensic” by covering some important track such as how Data is transferring between two nodes, what is “OSI 7 layer model” and Wireshark stores which layers information when capture the traffic between two networks.
As we know for transferring the data from one system to other we need a network connection which can be wired or wireless connection. But in actually transmission of data is not only depends upon network connection apart from that it involves several phases for transmitting data from one system to another which was explained by OSI model.
OSI stands for Open Systems Interconnection model which is a conceptual model that defines and standardizes the process of communication between sender’s and receiver’s system. The data is transfer through 7 layers architecture where each layer has a specific function in transmitting data over next layer.
Now have a look over given below image where we had explained the functionality of each layer in OSI model. So when data is transmitted by sender’s network then it will go in downward direction and data move from application layer to physical layer whereas when receiver will receive the transmitted data it will come in upward direction from physical layer to application layer.
Flow of Data from Sender’s network: Application > Presentation > Session > Transport > Network > Data Link > Physical
Flow of Data from Receiver’s network: Physical > Data Link > Network > Transport > Session > Presentation > Application
Examine Layers captured by Wireshark
Basically when a user opens any application for sending or receiving Data then he directly interacts with application layer for both operations either sending or receiving of data. For example we act as client when use Http protocol for uploading or Downloading a Game; FTP for downloading a File; SSH for accessing the shell of remote system.
While connecting with any application for sharing data between server and client we make use of Wireshark for capturing the flow of network traffic stream to examine the OSI model theory through captured traffic.
From given below image you can observe that wireshark has captured the traffic of four layers in direction of source (sender) to destination (receiver) network.
Here it has successfully captured Layer 2 > Layer 3 > Layer 4 and then Layer 7 information.
Ethernet Header (Data Link)
Data link layer holds 6 bytes of Mac address of sender’s system and receiver’s system with 2 bytes of Ether type is used to indicate which protocol is encapsulated i.e. IPv4/IPv6 or .
In wireahark Ethernet II layer represent the information transmitted over data link layer. From given below image you can observed that highlighted lower part of wireshark is showing information in Hexadecimal format where the first row holds information of Ethernet headers details.
So here you can get source and destination Mac address which also available in Ethernet Header.
The row is divided into three columns as described below:
| Ethernet header 14 bytes
| Destination MAC Address 6 Bytes
| Source MAC Address 6 Bytes
| Ether Type 2 Bytes
|
| Bits Color | Gray | Light Green | Pink |
| Hexadecimal value
| Fc:aa:14:6a:9a:a2 | 00:0c:29:d1:8e:0c | 0800 |
As we know Mac address of system is always represents in Hexadecimal format but Ether type are generally categories in given below ways.
| Ether Type | Hexadecimal Value |
| ARP: Address Resolution Protocol | 0x0806 |
| IPv4: Internet Protocol version 4 | 0x0800 |
| IPv6: Internet Protocol version 6 | 0x86dd |
| IEEE 802.1Q | 0x8100 |
Once again if you notice given below image then you can observe the highlighted text in Pink color is showing hex value 08 00 which indicates that here IPv4 is used.
IP Header (Network Layer)
IP header in wireshark described the network layer information which is also known as backbone of OSI model as it holds Internet Protocol version 4 complete details. Network layer divides data frame into packets and define its routing path through some hardware devices such as routers, bridges, and switches. These packets are identified through their logical address i.e. source or destination network IP address.
In Image of wireshark I have highlighted six most important values which contain vital information of a data packet and this information always flow in same way as they are encapsulated in same pattern for each IP header.
Now here 45 represent IPv4 header length while 40 is time to live (TTL) of packet and 06 is hex value for TCP protocol which means these values get change any things change i.e. TTL, Ipv4 and Protocol.
Therefore you can take help of given below table for examine TTL value for different operating system.
| Operating System | Hex Value TTL | Decimal value TTL |
| Windows | 80 | 128 |
| Linux | 40 | 64 |
| MAC | 39 | 57 |
Similarly you can take help of given below table for examine Protocol value for different operating system.
| Protocol | Hex Value | Decimal Value |
| ICMP | 1 | 1 |
| TCP | 6 | 6 |
| EGP | 8 | 8 |
| UDP | 11 | 17 |
From given below image you can observe Hexadecimal information of IP header field and using given table you can study these value to obtain their original value.
| IP header (20 bytes) | Header length | Total Length | TTL | Protocol | Source IP | Destination IP |
| Bits Color | Red | Orange | Yellow | Dark Green | Dark Brown | Black |
| Hex Value | 45 | 3c | 40 | 06 | C0.a8.01.68 | C0.a8.01.65 |
| Decimal value | 69 | 60 | 64 | 6 | 192.168.1.104 | 192.168.1.105 |
TCP Header (Transport layer)
Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) and Internet Control Message protocol (ICMP) are the major protocols as it gives host-to-host connectivity at the Transport Layer of the OSI model. It is also known as Heart of OSI model as it play major role in transmitting errors free data.
By examine Network Layer information through wireshark we found that here TCP is used for establishing connection with destination network.
We knew that a computer communicates with another device like a modem, printer, or network server; it needs to handshake with it to establish a connection.
TCP follow Three-Way-Handshakes as describe below:
- Client sends a TCP packet to the server with the SYN flag
- Server responds to the client request with the SYN and ACK flags set.
- Client completes the connection by sending a packet with the ACK flag set
Structure of TCP segment
Transmission Control Protocol accepts data from a data stream, splits it into chunks, and adds a TCP header creating a TCP segment. A TCP segment only carries the sequence number of the first byte in the segment.
A TCP segment consists of a segment header and a data section. The TCP header contains mandatory fields, and an optional extension field.
| Source Port | The 16-bit source port number, Identifies the sending port. |
| Destination Port | The 16-bit destination port number. Identifies the receiving port |
| Sequence Number | The sequence number of the first data byte in this segment. If the SYN control bit is set, the sequence number is the initial sequence number (n) and the first data byte is n+1. |
| Acknowledgment Number | If the ACK control bit is set, this field contains the value of the next sequence number that the receiver is expecting to receive. |
| Data Offset | The number of 32-bit words in the TCP header. It indicates where the data begins. |
| Reserved | Six bits reserved for future use; must be zero. |
| Flags | CWR, ECE, URG, ACK, PSH, RST, SYN, FIN |
| Window | Used in ACK segments. It specifies the number of data bytes, beginning with the one indicated in the acknowledgment number field that the receiver (the sender of this segment) is willing to accept. |
| Checksum | The 16-bit one’s complement of the one’s complement sum of all 16-bit words in a pseudo-header, the TCP header, and the TCP data. While computing the checksum, the checksum field itself is considered zero. |
| Urgent Pointer | Points to the first data octet following the urgent data. Only significant when the URG control bit is set. |
| Options | Just as in the case of IP datagram options, options can be either: – A single byte containing the option number – A variable length option in the following format |
| Padding | The TCP header padding is used to ensure that the TCP header ends and data begins on a 32 bit boundary. The padding is composed of zeros.
|
Different Types of TCP flags
TCP flags are used within TCP header as these are control bits that specify particular connection states or information about how a packet should be set. TCP flag field in a TCP segment will help us to understand the function and purpose of any packet in the connection.
| List of flags
| Description | Hex Value | Decimal Value |
| CWR | Congestion Window Reduced (CWR) flag is set by the sending host to shows that it received a TCP segment with the ECE flag set | 128 | 80 |
| ECE | ECN-Echo indicate that the TCP peer is ECN capable during 3-way handshake | 64 | 40 |
| URG | Indicates that the urgent pointer field is significant in this segment. | 32 | 20 |
| ACK | Indicates that the acknowledgment field is significant in this segment. | 16 | 10 |
| PSH | Push function to transfer data | 08 | 08 |
| RST | Resets the connection. | 04 | 04 |
| SYN | Synchronizes the sequence numbers. | 02 | 02 |
| FIN | Last packet from sender which means there is no more data. | 01 | 01 |
| NS | Nonce Sum flag used for concealment protection. | 00 | 00 |
From given below image you can observe Hexadecimal information of TCP header field and using given table you can study these value to obtain their original value.
Sequence and acknowledgement numbers are is major part of TCP, and they act as a way to guarantee that all data is transmitted consistently since all data transferred through a TCP connection must be acknowledged by the receiver in a suitable way. When an acknowledgement is not received, then the sender will again send all data that is unacknowledged.
| TCP Header | Bits Color | Hex Value | Decimal value |
| Source Port | Pink | ed f2 | 60914 |
| Destination Port (HTTP) | Lemon Yellow | 00 50 | 80 |
| Sequence Number | Dark Brown | 8c 44 36 e7 | 2353280743 |
| Acknowledgment Number | Grey | 00 00 00 00 | 0 |
| Flag (SYN) | Dark Yellow | 02 | 02 |
| Window size | Green | 72 10 | 29,200 |
| Checksum | Orange | 84 4c | 33,868 |
| Urgent Pointer | Light Brown | 00 00 | 00 |
| Options | Red | * | * |
Using given below table you can read Hex value of other Port Number and their Protocol services. Although these services operate after getting acknowledgement from destination network and explore at application layer OSI model.
In this way you can examine every layer of Wireshark for Network Packet Forensic.
| Ports Number | Services | Hex Value | Decimal Value |
| 21 | FTP | 15 | 21 |
| 22 | SSH | 16 | 22 |
| 23 | Telnet | 17 | 23 |
| 25 | SMTP | 19 | 25 |
| 53 | DNS | 35 | 53 |
| 80 | HTTP | 50 | 80 |
Author: AArti Singh is a Researcher and Technical Writer at Hacking Articles an Information Security Consultant Social Media Lover and Gadgets. Contact here
The post Network Packet Forensic using Wireshark appeared first on Hacking Articles.
from Hacking Articles http://ift.tt/2CQo7NK