/smokey

rust protocol analyzer (in dev)

Primary LanguageRustMIT LicenseMIT

cnote

rust protocol analyzer (early dev)

How it works

if not Open Suse (or maybe other linux variations)

first make sure rust is installed then clone the project then in the root of the project cargo run and the basic window should show up.

if OpenSuse (or maybe other linux variations)

cargo build --release \
&& sudo setcap cap_net_raw,cap_net_admin+eip target/release/cnote

if in Pop!_Os (in the cnote directory)

cargo build --release
sudo ./target/release/cnote

If you are linux, you may have to install the following dependencies:

dbus-x11
libgtk-3-dev

Supported protocols

Ethernet, IPv4, UDP, and TCP right now

base frame

#[derive(Default, Debug)]
pub struct EthernetFrame {
    pub id: i32,
    pub timestamp: String,
    pub header: EthernetHeader,
    pub payload: Option<Box<dyn Layer>>,
}

Layer is a trait object that gets implemented further down the line. Ever protocol it encapsulates implements the trait Layer
so
Ethernet -> IP -> TCP

Layers

Every packet implements the layer trait, layer implements the Send marker

Sniffers

Sniffers are the packet capture logic.

This is just a rough outline for anyone who reads this/myself so i know what im doing.

Each packet that implements layer handles the logic for the layer it encapsulates.

Milestones

  1. Establish a general framework for the backend that is a reasonable approach
    šŸ”µšŸ”µšŸ”µšŸ”µšŸ”µā¬œā¬œā¬œā¬œā¬œ 50%
  2. Logging -
    ā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œ 0 %
  3. Set up basic gui -
    šŸ”µšŸ”µā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œ 0 %
  4. Figure out how to handle 802.11 frame -
    ā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œ 0%
  5. Figure out how to highlight problem packets -
    ā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œā¬œ 0%