6 releases (breaking)

new 0.11.0 May 29, 2024
0.10.0 May 19, 2024
0.9.0 Apr 27, 2024
0.8.0 Apr 8, 2024
0.6.0 Feb 25, 2024

#18 in #data-link

Download history 158/week @ 2024-02-19 149/week @ 2024-02-26 5/week @ 2024-03-04 14/week @ 2024-03-11 14/week @ 2024-03-18 13/week @ 2024-03-25 40/week @ 2024-04-01 155/week @ 2024-04-08 19/week @ 2024-04-15 155/week @ 2024-04-22 22/week @ 2024-04-29 5/week @ 2024-05-06 201/week @ 2024-05-13 113/week @ 2024-05-20

370 downloads per month
Used in 12 crates (5 directly)

MIT license



Cross-platform networking library in Rust

Crates.io Documentation License


nex is a Rust library that provides cross-platform low-level networking capabilities.
It includes a set of modules, each with a specific focus:

  • datalink: Datalink layer networking.
  • packet: Low-level packet parsing and building.
  • packet-builder: High-level packet building.
  • socket: Socket-related functionality.

Upcoming Features

The project has plans to enhance nex with the following features:

  • More Protocol Support: Expanding protocol support to include additional network protocols and standards.
  • Performance Improvements: Continuously working on performance enhancements for faster network operations.


To use nex, add it as a dependency in your Cargo.toml:

nex = "0.11"

Using Specific Sub-crates

You can also directly use specific sub-crates by importing them individually.

  • nex-datalink
  • nex-packet
  • nex-packet-builder
  • nex-socket

If you want to focus on network interfaces, you can use the netdev.

for Windows Users

Please note that in order to send and receive raw packets using nex-datalink on Windows, npcap is required.

  1. Install Npcap, making sure to check Install Npcap in WinPcap API-compatible Mode during the installation.

  2. Download the Npcap SDK. Add the SDK's /Lib/x64 (or /Lib) folder to your LIB environment variable.

To simplify the process of downloading and installing npcap, you can use nex-npcap-helper. This crate facilitates the download and installation process, which can be helpful when distributing applications that utilize nex-datalink on Windows.

Build time requirements for optional feature

The cryptography provider for nex-socket's optional tls feature use aws-lc-rs. Note that this has some implications on build-time tool requirements, such as requiring cmake on all platforms and nasm on Windows.
Starting from v0.11.0, you can also continue to use ring as the cryptography provider (without additional dependencies) by specifying the tls-ring feature.


~351K SLoC