arcbox-proxy 0.4.23

Host-socket egress (UDP/ICMP), SOCKS5/HTTP-CONNECT tunnels, and inbound L2 relay for the ArcBox proxy datapath
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23

//! Proxy egress and inbound relay for the ArcBox datapath.
//!
//! Transport-agnostic building blocks that turn classified guest/host frames
//! into real network I/O, with no VM/VirtIO/device dependency:
//!
//! - [`socks5`] — all SOCKS5 (RFC 1928): the shared address codec, the CONNECT
//!   tunnel client ([`socks5::connect_via_socks5`]), and the UDP-ASSOCIATE client
//!   ([`socks5::Socks5UdpAssociation`]), connecting by hostname so Fake-IP
//!   destinations resolve on the proxy's side.
//! - [`http_connect`] — the HTTP CONNECT tunnel client.
//! - [`egress`] — proxies guest UDP/ICMP through real host sockets (bypassing
//!   kernel routing / VPN interference), optionally via the SOCKS5 proxy, and
//!   dispatches inbound datagrams through the [`inbound_relay`].
//! - [`inbound_relay`] — host → guest port forwarding by injecting crafted L2
//!   frames, plus the listener manager and `InboundCommand` channel.
//!
//! Extracted from `arcbox-net` so a host-level proxy can reuse the same egress
//! and relay machinery as the VM datapath.

pub mod egress;
pub mod http_connect;
pub mod inbound_relay;
pub mod socks5;