Hangs on TCP Connect after changing networks
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 1.8k
- Forks
- 465
- PR merge metrics
- No merged PRs in 30d
Description
After changing networks e.g. from Wi-Fi to Ethernet, the VPN does not automatically reconnect, it attempts to and then hangs at "MANAGEMENT: >STATE:1532337175,TCP_CONNECT,,,,,"
If I click the reconnect button within the GUI interface it reconnects immediately.
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
Start by reproducing a network change from Wi-Fi to Ethernet and compare the automatic reconnect with clicking the GUI reconnect button. Trace how the GUI handles the reported TCP_CONNECT state and the manual reconnect path. Done means the VPN reconnects automatically after the network changes without hanging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- desktop, networking, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100