-
Notifications
You must be signed in to change notification settings - Fork 36
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
What is the point of using ZeroTier? #60
Comments
Simple answer: Alternate answers:
|
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 :) |
Scratch that, we are explicitly trying to lock Parsec down: |
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, |
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 :)
…On Thu., 24 Dec. 2020, 12:05 pm SwiftWinds, ***@***.***> wrote:
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
<https://support.parsec.app/hc/en-us/articles/360001562772-All-Advanced-Configuration-Options>
and also according to a Parsec team member):
[image: image]
<https://user-images.githubusercontent.com/12981958/103050505-5707f300-4549-11eb-8398-b6b7a74c0780.png>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#60 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF5YVP7YQMGBIBLYWBTA6ODSWKOYJANCNFSM4VFG2IYQ>
.
|
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 |
Reopening until we've removed the |
Since Parsec uses the STUN protocol, what is the need for ZeroTier? I understand that if one is under a double NAT where even STUN breaks down, it makes sense, but AFAIK, this is rarely the case in most residential network situations (which I assume is where most gaming is).
The text was updated successfully, but these errors were encountered: