weron
gon2n
Our great sponsors
| weron | gon2n | |
|---|---|---|
| 15 | 1 | |
| 1,731 | 73 | |
| - | - | |
| 3.8 | 0.0 | |
| 7 months ago | about 1 year ago | |
| Go | Go | |
| GNU Affero General Public License v3.0 | GNU Affero General Public License v3.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
weron
-
hTorrent – A HTTP to BitTorrent gateway with seeking written in Go
Hey :) I totally agree! In most projects, I do the same (see https://github.com/pojntfx/weron). The only reason this isn't the case here is time, wrote this in 2 days :) Embedding is def. on the horizon.
-
ISP prevents me from forwarding ports. How would you recommend bypassing this restriction?
Also, maybe checkout weron: https://github.com/pojntfx/weron
-
Show HN: Weron – A Peer-to-Peer VPN Based on WebRTC Written in Go
n2n is neat! It is super simple to self-host the signaler in STUN/TURN in the case of weron as well: https://github.com/pojntfx/weron#1-start-a-signaling-server-... and `coturn` is even vendored through the Debian repos nowadays.
- GitHub - pojntfx/weron: Overlay networks based on WebRTC.
- Weron – A Peer-to-Peer VPN Based on WebRTC Written in Go
gon2n
-
Show HN: Weron – A Peer-to-Peer VPN Based on WebRTC Written in Go
Hi! n2n was a huge inspiration for the project, in fact I wrote Go bindings for n2n before starting it: https://github.com/pojntfx/gon2n
Weron also allows tunneling - just specify a TURN server on `--ice` and enable `--force-relay`, in which case it will probably scale to well over 100 nodes ^^ The signaling servers are fully horizontally scalable, so that you can benefit from a faster backbone on a global scale scenario - Redis coordinates messages, kicks etc. between them and a Postgres database maintains central state, such as credentials for persistent communities and client counts.
In terms of key rotation & encryption - weron heavily depends on DTLS as provided by Pion/WebRTC and thus inherits similar security properties. It is not possible to disable encryption of WebRTC, but tbf the performance benefits of using plain SCTP don't seem to be worth it as the RTT latency and resulting decrease in throughput[1] is the dominant performance bottleneck.
[1] https://tuhat.helsinki.fi/ws/portalfiles/portal/167373638/Es...
What are some alternatives?
n2n - Peer-to-peer VPN
turn - Pion TURN, an API for building TURN clients and servers
ziti-doc - Documentation describing the usage of the Ziti platform.
netbird - Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
go-daemon - A library for writing system daemons in golang.
Pion WebRTC - Pure Go implementation of the WebRTC API
stfs - Simple Tape File System (STFS), a file system for tapes and tar files.