New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Peertube doesn't work with NAT/LAN #1274
Comments
Suggestion: Make a native client, at least for Windows and Android. |
I wonder if this is a bug in one of the upstream dependencies, like webtorrent for instance |
Nope. It's just that there's no Local Peer Discovery on the web, you have to have a tracker. |
Related to webtorrent/webtorrent#1136? |
fwiw, WebRTC can work between clients on the local LAN if you are willing to establish those connections via a remote tracker. I'd expect that normally we don't publish RFC1918 (private) IPs to the tracker, even if WebRTC makes this information available to the client, but it could be useful to publish that info in such a way that clients behind the same public IP (same NAT, presumably) can find other RFC1918 IPs on that network. |
if that can be done, please do my dial-up will thank you |
So I think it's more a WebTorrent issue |
What happened?
Peertube doesn't benefit from a LAN's internal links, instead being limited to the internet connection speed.
What do you expect to happen instead?
Peertube should benefit from local peers, just like torrents.
Steps to reproduce:
Setup a LAN on a dial-up (56kbps) connection
Install peertube on a remote server
Access that peertube from multiple computers in the LAN
The text was updated successfully, but these errors were encountered: