netru

A Rust crate for cross-platform network libraries and utilities. The goal is to build a comprehensive collection of network tools, libraries, and helpers — all under one dependency.

Installation

[dependencies]
netru = "0.1"

Disable the utils feature to drop the iptools dependency:

netru = { version = "0.1", default-features = false }

Usage

All types are available directly at the crate root:

use netru::{Sysproxy, Autoproxy};

CIDR to Wildcard

Useful for building bypass lists. Requires the utils feature (on by default).

use netru::utils::ipv4_cidr_to_wildcard;

let w = ipv4_cidr_to_wildcard("192.168.1.0/24")?; // ["192.168.1.*"]
let w = ipv4_cidr_to_wildcard("10.0.0.0/8")?;     // ["10.*"]

Modules

Module	Description	Docs
sysproxy	OS system proxy get/set (HTTP, HTTPS, SOCKS, PAC)	src/sysproxy/README.md

Binaries

Binary	Description	Usage
proxy_ctl	Toggle system proxy on/off from the command line	cargo run --bin proxy_ctl -- --enable 127.0.0.1:7890

# Enable system proxy
cargo run --bin proxy_ctl -- --enable 127.0.0.1:7890

# Disable system proxy
cargo run --bin proxy_ctl -- --disable

# Check current state
cargo run --bin proxy_ctl -- --check

Features

Feature	Default	Description
utils	✅	CIDR/IP utility helpers (pulls in iptools)

Development

Prerequisites

• Rust 1.80+
• macOS: networksetup (built-in)
• Linux: gsettings (GNOME) or kreadconfig5/kreadconfig6 (KDE)
• Windows: no extra dependencies

Build

cargo build
cargo build --release

Test

# Run all tests
cargo test

# Run only unit tests — safe, does not touch system proxy settings
cargo test utils

# Run integration tests — temporarily modifies your system proxy
cargo test -- --test-threads=1

test_system_enable and test_auto_enable modify your system proxy settings during the test and restore a disabled state when complete. They are serialized with serial_test to avoid races.

Lint & Format

cargo fmt
cargo clippy

Publish

1. Check the package is valid:

cargo package --list   # preview files included in the published crate
cargo publish --dry-run

2. Login to crates.io (one-time):

cargo login
# paste your API token from https://crates.io/settings/tokens

3. Bump the version in Cargo.toml, then publish:

cargo publish

Project Structure

netru/
├── Cargo.toml
├── README.md
├── src/
│   ├── lib.rs              # Flat re-exports (pub use sysproxy::*)
│   ├── bin/
│   │   └── proxy_ctl.rs    # CLI tool for toggling system proxy
│   └── sysproxy/
│       ├── README.md       # Sysproxy module docs
│       ├── mod.rs          # Types, Error, Result
│       ├── macos.rs
│       ├── windows.rs
│       ├── linux.rs
│       └── utils.rs
└── tests/
    └── test.rs

Internal modules live under src/<module>/ but are never exposed as nested paths — everything is re-exported flat at netru::*. When a new module grows too many types, it gets its own subdirectory following the same pattern.

Roadmap

Type	Description	Status
Sysproxy / Autoproxy	OS system proxy get/set	✅ Stable
NetInfo	Network interface enumeration and stats	Planned
DnsResolver	Async DNS resolver with caching	Planned
PortScanner	TCP/UDP port scanner	Planned
ProxyChecker	Proxy health checker (latency, anonymity)	Planned
PacFile	PAC file parser and evaluator	Planned
NetMonitor	Real-time bandwidth and connection monitor	Planned
Traceroute	Cross-platform traceroute	Planned
HttpProbe	HTTP connectivity prober	Planned

Contributing

To add a new module:

1. Create src/<module>/mod.rs with its types and logic
2. Add platform-specific files as src/<module>/<platform>.rs if needed
3. Re-export the public types in src/lib.rs
4. Add an entry to the Roadmap table above
5. Gate heavy dependencies behind an optional feature flag

License

MIT