zerotier / zerotier/ZeroTierOne
After inactive time, ping and RDP to remote Windows computer do not work via Zerotier
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 17.1k
- Forks
- 2k
- PR merge metrics
- No merged PRs in 30d
Description
Zerotier Windows client version: 1.12.2
If there is no connection to the Windows computer for a long time (more than 6 hours), the connection is lost through Zerotier. Neither ping nor RDP works. This is solved by connecting with Teamviewer, AnyDesk or OpenVPN to the remote computer. As a connection is established with another program, Zerotier starts pinging and RDP.
It feels like Zerotier falls asleep and then suddenly wakes up. At the same time, ping to RDP to this computer works on the local network, but does not work on the Zerotier network. Zerotier is just starting to work by connecting to the computer in a different way. This has been observed on several different Windows 10 computers.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is identified. Start by reproducing the failure on a Windows 10 computer running ZeroTier 1.12.2 after more than six hours without a connection, then compare local-network and ZeroTier ping/RDP behavior before and after using TeamViewer, AnyDesk, or OpenVPN. Done means the cause of the inactive-period failure is identified and the ZeroTier connection remains usable without another program waking it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100