weron
turn
Our great sponsors
| weron | turn | |
|---|---|---|
| 15 | 3 | |
| 1,731 | 1,699 | |
| - | 3.4% | |
| 3.8 | 7.5 | |
| 7 months ago | about 24 hours ago | |
| Go | Go | |
| GNU Affero General Public License v3.0 | MIT License |
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
turn
-
Using WebTransport
> dedicated signalling
For my small projects I run my HTTP + WebRTC in the same server. My signaling is one POST. Maybe I am missing the complexity, but I don't feel any additional pain compared to running any network service?
> STUN Karate
Mind explaining more? I use https://github.com/pion/turn and run my STUN server embedded in my HTTP server. I do do anything but point my `PeerConnection` at `my-service.com`
-
Show HN: Weron – A Peer-to-Peer VPN Based on WebRTC Written in Go
There is a very neat implementation of a TURN from Pion
https://github.com/pion/turn
-
How do I deploy a TURN server for WebRTC apps on heroku?
I've tried node-turn in a node.js server, tried to execute pion/turn binaries directly so far but with no luck. `node-turn` works if I run locally and test it with my public ip address but the same doesn't work on heroku.
What are some alternatives?
n2n - Peer-to-peer VPN
livekit-server - Scalable, high-performance WebRTC SFU. SDKs in JavaScript, React, React Native, Flutter, Swift, Kotlin, Unity/C#, Go, Ruby and Node. [Moved to: https://github.com/livekit/livekit]
gon2n - Go bindings, management daemons and CLIs for n2n edges and supernodes.
Pion WebRTC - Pure Go implementation of the WebRTC API
netbird - Connect your devices into a single secure private WireGuard®-based mesh network with SSO/MFA and simple access controls.
go-stun - A go implementation of the STUN client (RFC 3489 and RFC 5389)
stun - Fast RFC 5389 STUN implementation in go
ziti-doc - Documentation describing the usage of the Ziti platform.
node-turn - Node-turn is a STUN/TURN server for Node.JS
stfs - Simple Tape File System (STFS), a file system for tapes and tar files.