4 ms·
> ...it uses WebRTC to make the direct peer connections. This allows us to make use of WebRTC's NAT traversal tricks, as well as the fact that it can be used in
by crazygringo 7y ago
> ...it uses WebRTC to make the direct peer connections. This allows us to make use of WebRTC's NAT traversal tricks, as well as the fact that it can be used in browsers.
But I'm assuming it can't break through all NAT routers, right? A good portion of people still won't be able to use this?
A service usable by everyone would require STUN and TURN servers to be set up, no?
Or has WebRTC made advances I'm unaware of?
- Sean-Der 7y agoI don't have any hard numbers, but I have heard ~85% ICE success rate with out TURN. But you are right, in some cases WebRTC will fail without TURN. Just no one wants to pay to run those servers :) I would love to see TCP hole punching in ICE, but it sounds like it is super hard to get right. Consumer internet does a lot better, lots of those failures come from Government/Military/Medical I bet.
- jackewiehose 7y agoYou always need a at least a STUN server and in my experience that 85% isn't remotely true. For example STUN-only never worked from mobile internet (only tested some german providers).
- algesten 7y agohow would TCP hole punching even work? TCP has state and a handshake. UDP doesn't.
- folmar 7y ago> Just no one wants to pay to run those servers :) No, it's the users that don't want their (meta)data inspected by a random third party in transit. This is why I don't use filepizza
- saljam 7y agoThis uses STUN servers to help it poke through NATs. (That's what I mean by "WebRTC's NAT traversal tricks") There's no TURN server set for this, but it shouldn't be hard to add one. There are NATs where you'd need one to relay all the traffic, but these seem to be relatively rare nowadays. If anyone has any actual statistics on these I'd appreciate it!
- majke 7y agoWhich one? Which STUN server are you using?
- adrianpike 7y agoLooks like Google's: https://github.com/saljam/webwormhole/blob/f542b26fb2fa3282023d7836d679bb4b758c7e97/web/main.js#L150 https://github.com/saljam/webwormhole/blob/f542b26fb2fa32820...
- lioeters 7y agostun:stun.l.google.com:19302 Source: https://github.com/saljam/webwormhole/blob/8f707583d68173de3d380525244145099a3a9721/cmd/ww/main.go#L27-L28 https://github.com/saljam/webwormhole/blob/8f707583d68173de3...
- saljam 7y agoThe website uses Google's. On command line it's an option and Google's is default. I'd like to make the signalling server also a STUN server at some point.
- crazygringo 7y agoOh that's interesting... I had no idea there were publicly available STUN servers like that. But way back in 2014 a Google employee does seem to have confirmed it's free to use, but comes without guarantees. [1] https://groups.google.com/d/msg/discuss-webrtc/shcPIaPxwo8/F8Vc8QlIyn0J https://groups.google.com/d/msg/discuss-webrtc/shcPIaPxwo8/F...
- 7y ago
- bscphil 7y ago> But I'm assuming it can't break through all NAT routers, right? A good portion of people still won't be able to use this? > A service usable by everyone would require STUN and TURN servers to be set up, no? Anecdata, of course, but I haven't been able to reliably use any of these WebRTC based file transfer services (file.pizza, instant.io, etc etc). Testing mostly between two computers on the same subnet. Sometimes they work for a little while, at surprisingly low speeds (for two computers connected to the same wireless access point), sometimes I can let them sit for an hour and never get a connection. I've learned to not even bother trying them, it just wastes time. That said, magic-wormhole (the original) works fine between the same devices, so maybe I'll see if something is somehow different about this implementation. Edit: ah yes, this service hangs indefinitely on "connecting". You love to see it. (Firefox on Linux - firewall disabled specifically for this test - and Safari on macOS) Edit: seems to be working in Chrome (Linux) to Firefox (Android). Not sure what the difference is.
- anderspitman 7y agoAlso didn't work for me on Firefox/Linux, between 2 tabs.
- bscphil 7y agoHmm, maybe this is a classic "didn't bother testing on Firefox" situation. I wonder if anyone on a different OS can confirm.
- saljam 7y agoI developed it mainly on Firefox on macOS. I'd love to figure out why it didn't work for you. Do you get anything on about:webrtc while trying to connect?
- bscphil 7y agoThanks for the reply. I did the following for you: 1. Opened about:webrtc, clicked "start debugging". 2. Opened a WebWormhole on one tab. 3. Copy / pasted the code into WebWormhole on another tab. Got something like "invalid key". 4. Try again steps two and three. Got endless "connecting" message this time. 5. Stop debugging. No log file /tmp/WebRTC.log was created, so I clicked "save page". Used sed to replace my public IP address with x.x.x.x and uploaded here for you: https://ipfs.io/ipfs/QmTM1ZSRk1xqfMd2FF23YzWxHpqjJ2B6kGFQqPdhRszgHa https://ipfs.io/ipfs/QmTM1ZSRk1xqfMd2FF23YzWxHpqjJ2B6kGFQqPd... I hope this gives you enough information to fix the problem. I'd like to be able to use these tools too. I suppose it could be addon related, but another user confirmed the problem for Firefox / Linux. It would be useful to be able to detect various problems and report them to the user instead of hanging on "connecting".