What is the point of using ZeroTier? about gcloudrig HOT 7 OPEN

Reopening until we've removed the Protect-Parsec function in the powershell module

from gcloudrig.

Simple answer:
Parsec doesn't work all the time, and Zerotier is just one (of many) ways to have a sensible back-door at a network level.

Alternate answers:

• Parsec doesn't always automatically login, which can leave you stranded if that's your only way to access your rig, so RDP/VNC are still good things to keep on standby.
• It's poor practice to leave RDP/VNC ports (or any ports for that matter) exposed on the public internet for inbound connections, unless you're actually expecting traffic from many uncontrolled locations.
• I'm a Steam Controller fanboy, so being able to use Zerotier and the Steam Link app on an Android phone is pretty handy for a quick gaming session on the go.
• Because old-school local LAN party?

from gcloudrig.

I haven't checked recently but I'm fairly sure that Parsec doesn't even use the ZeroTier connection; this could be due to Windows assigning it a different interface metric or the Parsec clients just preferring their own hole-punched routes. It would be interesting to know for sure and see if this is introducing any extra latency, so I'll leave this ticket open until I have an answer :)

from gcloudrig.

Scratch that, we are explicitly trying to lock Parsec down:
https://github.com/putty182/gcloudrig/blob/6662ad3af256d2b61865aacd69a02857d1c1ac51/gcloudrig.psm1#L773-L788

from gcloudrig.

It would be interesting to know for sure and see if this is introducing any extra latency

I'm a bit confused. Wouldn't ZeroTier, if anything, increase latency? You seem to imply that Parsec bypassing ZeroTier may introduce extra latency, but I'm not sure I understand how that would be the case.

Also, looking through the code, network_ip_address no longer does anything. It's deprecated (not on the website and also according to a Parsec team member):

from gcloudrig.

from gcloudrig.

Not at all - my point was that Zerotier might have no effect on latency because Parsec traffic isn't routed over it. Thanks for confirming that this setting in Parsec is deprecated :)

OK, I see. :) Just confirming that you didn't recommend it out of "performance reasons" because that wouldn't be accurate.

I guess this issue is resolved because what you mentioned in #60 (comment) are good reasons to keep it. Optionally, you can get rid of that Protect-Parsec function since it does nothing and only serves to possibly confuse your future self.

from gcloudrig.