Skip to content
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

Reduce traffic in idle case, and TCP only option? #768

Closed
iandol opened this issue May 29, 2018 · 2 comments
Closed

Reduce traffic in idle case, and TCP only option? #768

iandol opened this issue May 29, 2018 · 2 comments
Labels
Status: Backlog Older issues that are awaiting resolution

Comments

@iandol
Copy link

iandol commented May 29, 2018

I work at a research university and am behind a NAT and firewall and I am not supposed to run something like SSH. Anyway, I set up ZeroTier and for a while was extremely happy as everything just worked and I could connect easily across work/home/mobile (ZT is awesome, even for non expert like myself!). I was later told that there was "suspicious" traffic coming from my machine and that I must reinstall the OS immediately or be permanently disconnected from the net. I simply disabled ZeroTier and was told all was back to normal. So I would like a mode whereby ZT works but does not create so much P2P traffic.

Here is a chat I had with someone on ZT community channel:

Hi, I love ZeroTier and have used it to connect my work and home machines together. But I was recently told by my IT manager that my work machine was creating suspicious traffic and that I must reinstall my machine or disconnect it permanently from the internet. I have no other network apps and by disabling ZeroTier and rechecking, my IT person was satisfied the "suspicious traffic stopped". How can I configure ZeroTier to act somewhat more "stealthily"? If not, can anyone recommend software that is similar to ZeroTier (I think I only know ngrok, freelan and hamachi).

zt-janjaap 16:04 It sounds to me your company policy won't allow you to be connected to non-company vpn's anyway, although it might technically feasible. If only http/s traffic is allowed, you could setup a personal gateway (on the cloud or at home if you can expose http/s), using something like https://github.com/jpillora/chisel

I work at a research university in China, and the admin doesn't really know much about anything other than their automated system flagged abnormal traffic We are not supposed to run VPNs either, but I use a shadowsocks based VPN which is not flagged. What happens if I turn multicast off in ZT, will that limit some of the P2P traffic? I am a neuroscientist, and while I'm studying another highly complex network, I am not a computer networking person. So sorry for any dumb questions in advance

zt-janjaap 17:23 No problem! No, I don't think at the moment there is something you can do to limit the peer traffic. ZeroTier will always keep trying to find a direct path, using nat punching techniques. I think it could be a feature request to be added: do not try to established direct paths except for allowed hosts / networks that are know to be directly reachable on the LAN. All other traffic would then be proxied through the global roots or your own moon. This would limit the number of peers to communicate with and reduce chatter on your local network.

@janjaapbos
Copy link
Contributor

It would be nice to have the option to use websocket only, with the roots and your own moon. This will help in locked down environments where no udp traffic is allowed.

@adamierymenko adamierymenko added the Status: Backlog Older issues that are awaiting resolution label May 29, 2018
@adamierymenko adamierymenko changed the title [Feature Request] ZT Stealth mode a.k.a generate less traffic if possible Reduce traffic in idle case, and TCP only option? May 29, 2018
@adamierymenko
Copy link
Contributor

see #867

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Backlog Older issues that are awaiting resolution
Projects
None yet
Development

No branches or pull requests

3 participants