Publish PMS with "hole punching" methode

Feature Suggestions
1

I think it would be nice, if we get the ability to publish our server with “hole punching”.

We know that e.g. on skype, teamviewer or google talk.

With hole punching we get following advantages.

  • no portforwarding need (client connection handled bei myplex)
  • easy encrypting traffic
  • no limitations, especially VPN will works without problems


    I hope this is possible and we can get this:-)


    http://en.m.wikipedia.org/wiki/UDP_hole_punching
2

Plex streaming is all based around TCP, specifically since this is the NATIVE method used by devices such as iOS devices.

Also the webui and Sync are based around TCP.

Going full UDP is something that would require almost a complete rewrite of plex or a duplication of most existing functions.

3

So its not possible or not worth to do it?

I think that would be a great feature.

I dont know enough about this technology, but I think its possible to use TCP with hole punching.

http://en.wikipedia.org/wiki/TCP_hole_punching

4

Probably a good read for anyone wanting to do this:

http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat/

The problem is that no single solution for NAT traversal will work in all situations -- and it can get quite complicated to work around some situations (like having to maintain 3rd party servers to assist traversal where it's the only option).

How many running Plex are behind NAT that they are unable to forward ports through (no administrative access to the firewall)?  I know many wireless providers put clients behind NAT (you don't get a public IP), but wireless doesn't seem like a good option to serve media from anyway. 

5

Probably a good read for anyone wanting to do this:

http://nutss.gforge.cis.cornell.edu/pub/imc05-tcpnat/

The problem is that no single solution for NAT traversal will work in all situations -- and it can get quite complicated to work around some situations (like having to maintain 3rd party servers to assist traversal where it's the only option).

How many running Plex are behind NAT that they are unable to forward ports through (no administrative access to the firewall)?  I know many wireless providers put clients behind NAT (you don't get a public IP), but wireless doesn't seem like a good option to serve media from anyway. 

Publishing to the new cloudsync feature also gets around this to a degree, but only for synced content.

6

2021 clean-up: duplicate