Win10 to Win10 on local LAN always immediately finishes despite duration
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 5.9k
- Forks
- 406
- PR merge metrics
- No merged PRs in 30d
Description
Running "ethr -c 172.16.2.99" for example, to connect between Win10 PCs on local LAN always yields "Ethr done, connection terminated" as soon as I run it. Works perfectly fine when connected to between server/client on the same PC (-s and -c on localhost). But using the network doesn't work. Windows Firewall is set to allow, the server process logs a connection for a split second. Client never really stays connected, even with -d set to a longer time (not that the default 10 seconds works either) Tested LAN and WLAN. Is there something I'm doing wrong?
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
Reproduce the issue with ethr -c 172.16.2.99 and a longer -d value, comparing it with the working localhost server/client setup. Trace the client and server connection lifecycle for the LAN case; done means a Windows-to-Windows connection remains active for the requested duration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100