Search Results for "protocol stack"

S-UI is an advanced web-based management panel built on top of SagerNet and Sing-box, designed to simplify the configuration and monitoring of proxy and networking services through an intuitive graphical interface. It provides a centralized dashboard where users can manage inbound and outbound connections, configure routing rules, and monitor traffic usage in real time. The platform supports multiple protocols and clients, making it flexible for different networking scenarios such as proxy...

paqet is a bidirectional packet-level proxy that transports traffic over raw packets instead of relying on the host operating system’s normal TCP/IP stack. It forwards traffic between a local client and a remote server using KCP as the reliable transport layer. The project is written in Go and is aimed at users who need a low-level tunnel that can operate in restricted or heavily filtered network environments. It is described as an alpha-stage tool, so compatibility and protocol behavior may change between releases. ...

...It also includes HTTPS-specific server and client modes that can map local HTTP services to subdomains under a configured domain. Zoro is designed around minimal configuration, making it practical when users need a quick way to publish a private service without a full reverse proxy stack. Its main value is straightforward local-to-public service exposure across different protocol types.

Noise is a lightweight and high-performance framework for building distributed peer-to-peer (P2P) systems in Go. Designed to be modular and easy to use, Noise abstracts away the complexity of building scalable networked applications, enabling developers to focus on protocol logic rather than low-level networking. It offers an actor-model inspired concurrency design and supports peer discovery, messaging, and transport encryption out of the box. Suitable for applications like decentralized...

netstack is a userspace TCP/IP networking stack written in Go that implements core IPv4/IPv6 protocols with a focus on correctness, isolation, and testability. By running entirely in user space, it avoids kernel dependencies and can be embedded into sandboxes, virtualized environments, or custom appliances. Its architecture models NICs, link endpoints, route tables, and protocol engines as composable interfaces, enabling precise control over packet flow and easy mocking in tests. ...

...On BSD-derived systems such as OSX, we use tools like ipfw and pfctl to inject failure. On Linux, we use iptables and tc. Comcast is merely a thin wrapper around these controls. Windows support may be possible with wipfw or even the native network stack, but this has not yet been implemented in Comcast and may be at a later date. On Linux, Comcast supports several options: device, latency, target/default bandwidth, packet loss, protocol, and port number.