Autobahn

A remote shell, TCP tunnel and HTTP proxy for Replit.

Hybrid SSH/HTTP server for Replit. Based on leon332157/replish.

Autobahn runs a WebSocket server using a special protocol, connected to a TCP-WebSocket proxy server. Autobahn intercepts incoming traffic and redirects it either through to already-listening servers on the computer, or onto the WebSocket server.

Licensed under the GNU GPL (3.0 or later).

Operation

At startup, Autobahn's server will either load a specified port from a configuration file, or scan directly for listening ports. The port eventually chosen - either automatically when only one, or by the user when multiple are detected - is forwarded to the proxy server.

The proxy server listens on port 3321, and detects HTTP packets from the stream. These HTTP are scanned, and rerouted to the Autobahn WebSocket server if they pointing to "/__atbws". Other packets are sent to the port passed from the initialiser.

The main Autobahn server is a WebSocket server listening on port 3322, and internally creates sessions and converts TCP sockets into WebSockets, before being passed onto the proxy server. The WebSockets use a special protocol which allows them to authenticate, pass messages, and create a remote shell or TCP tunnel.

Architecture

Library + CLI-Tool to measure the TTFB (time to first byte) of HTTP requests. Additionally, this crate measures the times of DNS lookup, TCP connect and TLS handshake.

TTFB: CLI + Lib to Measure the TTFB of HTTP/1.1 Requests Similar to the network tab in Google Chrome or Mozilla Firefox, this crate helps you find the

24 Dec 1, 2022

UDP proxy with Proxy Protocol and mmproxy support

udppp UDP proxy with Proxy Protocol and mmproxy support. Features Async Support Proxy Protocol V2 SOCKET preserve client IP addresses in L7 proxies(mm

10 Dec 18, 2022

Web3-proxy: a fast caching and load balancing proxy for web3 (Ethereum or similar) JsonRPC servers.

web3-proxy Web3-proxy is a fast caching and load balancing proxy for web3 (Ethereum or similar) JsonRPC servers. Signed transactions (eth_sendRawTrans

55 Jan 8, 2023

A simple cross-platform remote file management tool to upload and download files over HTTP/S

13 Dec 30, 2022

An easy-to-use tunnel to localhost built in Rust. An alternative to ngrok and frp.

rslocal English | 中文 What is rslocal? Rslocal is like ngrok built in Rust, it builds a tunnel to localhost. Project status support http support tcp su

220 Jan 7, 2023

A proxy implement with http / socks5 in-bound and vmess out-bound, written in Rust and tokio.rs

tokio-vmess an Asynchronous proxy implement with http / socks5 in-bound and vmess out-bound, written in Rust and tokio Run example first, Fill out the

7 Oct 3, 2022

♻ A simple and efficient Gemini-to-HTTP proxy written in Rust.

September A simple and efficient Gemini-to-HTTP proxy written in Rust. Usage Docker $ docker run -d [ -e ROOT="gemini://fuwn.me" ] [ -e PORT="8080"] [

10 Jul 2, 2022

Reverse proxy for HTTP microservices and STDIO. Openfass watchdog which can run webassembly with wasmer-gpu written in rust.

The of-watchdog implements an HTTP server listening on port 8080, and acts as a reverse proxy for running functions and microservices. It can be used independently, or as the entrypoint for a container with OpenFaaS.

7 Sep 15, 2022

Hudsucker is a MITM HTTP/S proxy written in Rust.

hudsucker Hudsucker is a MITM HTTP/S proxy written in Rust. Features Modify HTTP/S requests Modify HTTP/S responses Modify websocket messages Usage Fo

86 Dec 25, 2022

Comments

Properly document protocol

There is currently no simple documentation for the WebSocket-based protocol used for communicating between client and server. As it is a binary protocol, it is particularly difficult to understand purely from inspection, and so documentation would be useful.
documentation

opened by 19wintersp 0
Improve interactive user input

Currently, user input is read raw from the Stdin provided by the standard library. This works, however is insufficient for various purposes: an example of this is the password input on the client side, which does not hide the typed characters as would be expected. Adding dialoguer (or a similar library) would allow for this to happen much more easily.
enhancement client server

opened by 19wintersp 1
Use `anyhow` for error management

Currently, only io::Result is used as the return type on functions which can return errors, which leads to isses such as #2. Using anyhow instead will allow better error handling and effectively address these issues.
enhancement client server

opened by 19wintersp 0