https://github.com/justin-pyne/compdetect

A C-based project for detecting network compression using two approaches: a cooperative client/server application and a standalone application with raw socket operations.
https://github.com/justin-pyne/compdetect

c linux network-programming

Last synced: 2 months ago
JSON representation

A C-based project for detecting network compression using two approaches: a cooperative client/server application and a standalone application with raw socket operations.

• Host: GitHub
• URL: https://github.com/justin-pyne/compdetect
• Owner: justin-pyne
• Created: 2025-03-10T23:18:13.000Z (2 months ago)
• Default Branch: main
• Last Pushed: 2025-03-10T23:27:54.000Z (2 months ago)
• Last Synced: 2025-03-11T00:25:05.468Z (2 months ago)
• Topics: c, linux, network-programming
• Language: C
• Homepage:
• Size: 1.95 KB
• Stars: 0
• Watchers: 1
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# CompDetect: End-to-End Network Compression Detection

This repository contains two related projects for detecting network compression:

- **Client/Server Application (Part I):**  

  A cooperative application where the client sends configuration information and two sets of UDP packet trains (one with low-entropy data and one with high-entropy data) to the server. The server measures the packet train arrival times to decide if compression is present.

- **Standalone Application (Part II):**  

  A non-cooperative application that uses raw sockets. It sends a head SYN, a train of UDP packets, and a tail SYN packet. The application listens for two RST responses and calculates the timing difference to detect compression.

## Project Overview

### Client/Server Application

- **Pre-Probing Phase:**  

  The client reads a configuration file (which includes parameters like server IP, UDP/TCP port numbers, payload size, etc.) and sends it via TCP to the server.

- **Probing Phase:**  

  The client sends two UDP packet trains:

  - **Low-Entropy Train:** UDP packets with payloads of zeros.

  - **High-Entropy Train:** UDP packets with payloads of random bits (using `/dev/urandom`).

  

  Each packet starts with a 16-bit packet ID.

- **Post-Probing Phase:**  

  After processing the received packets, the server computes the time differences between the first and last packets in each train. If the high-entropy train takes more than 100 ms longer than the low-entropy train, the server concludes that compression is present and sends the result back via TCP.

### Standalone Application

- Uses raw sockets to send:

  - A **head SYN** packet.

  - A UDP packet train.

  - A **tail SYN** packet.

- It listens for RST responses from the target. The time difference between the arrival of these RST packets is used to determine whether network compression is present.