Search Results for "livekit-cli"

Sing-box is a universal proxy platform written in Go with support for servers and clients across platforms. It handles multiple proxy protocols with advanced routing, supports TUN-based transparent proxying, and offers both CLI and native graphical clients.

NextDNS protects you from all kinds of security threats, blocks ads and trackers on websites and in apps and provides a safe and supervised Internet for kids, on all devices and on all networks. Determine your threat model and fine-tune your security strategy by enabling 10+ different types of protections. Use the most trusted threat intelligence feeds containing millions of malicious domains, all updated in real-time. Go beyond the domain, we analyze DNS questions and answers on-the-fly (in...

...Instead of traditional VPN server infrastructure, Tailscale uses a coordination service to authenticate devices and exchange connection information, enabling automatic NAT traversal and minimal manual setup. The project includes a daemon (tailscaled) and a CLI tool that run on major operating systems, and it also forms the basis for the official clients on platforms like iOS and Android, though those have GUI wrappers not fully in this repository.

OmniEdge is an Open source p2p layer 2 , zero-config mesh VPN infrastructure, a traditional VPN, AWS VPC, Ngrok, DDNS alternative. No central server, easy to scale with less maintenance. What happens in intranet, stays in in intranet.

BoringTun is a high-performance, portable implementation of the WireGuard VPN protocol written in Rust, designed so that developers and system integrators can run WireGuard tunnels entirely in user space across a variety of operating systems without kernel modules. It implements the core WireGuard protocol — including key exchange, encryption (ChaCha20-Poly1305), and authenticated transport — while omitting platform-specific tunneling stacks, allowing embedment in custom VPN client...

JRF is a client/server application that allows to extend local storage to other computers running the JRF Server. It has been designed for ultra-simplicity, **not for security!** It does not request for authentication when accessing files on a remote server, nor does it prevent access to files or directories. It has been designed for already-secured networks (e.g. LANs or inside VPNs), where file-sharing setup is tedious (or impossible). Basic access configuration/restriction should be...