Search Results for "web based system"

frp stands for exactly what it is: a fast reverse proxy. It helps you expose a local server behind a NAT or firewall to the Internet. It is currently under development, but already supports TCP and UDP, as well as HTTP and HTTPS protocols where requests can be forwarded to internal services by domain name. It also has a P2P connect mode and many other nifty features. These include configuration files, environment variables, a dashboard that shows you frp's status and proxies' statistics...

GOST, or GO Simple Tunnel, is a flexible tunneling and proxy tool written in Go for building secure traffic forwarding chains. It supports proxying, port forwarding, reverse proxying, and tunnel-based access to services behind NAT or firewalls. The project is designed around protocol composition, allowing users to combine multiple protocols into multi-level forwarding chains. It can handle TCP and UDP forwarding, transparent proxying, DNS proxying, TUN/TAP workflows, and tun2socks scenarios. GOST also includes operational features such as load balancing, routing control, admission control, rate limiting, dynamic configuration, Prometheus metrics, and a Web API. ...

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...

...It is implemented by using the pure algorithm, and is not responsible for the sending and receiving of the underlying protocol (such as UDP), requiring the users to define their own transmission mode for the underlying data packet, and provide it to KCP in the way of callback. Even the clock needs to be passed in from the outside, without any internal system calls. The entire protocol has only two source files of ikcp.h, ikcp.c, which can be easily integrated into the user's own protocol stack. You may have implement a P2P, or a UDP-based protocol, but are lack of a set of perfect ARQ reliable protocol implementation, then by simply copying the two files to the existing project, and writing a couple of lines of code, you can use it.