When connected using wintun driver dns names are not resolved first 3-5 seconds
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 14.6k
- Forks
- 3.4k
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
When using wintun OpenVPN reports that connection was established but actually there is no connection during next 3-5 seconds.
To Reproduce
Write command ping <some_domain_name> in command line.
Then connect using wintun driver on Windows (I am connecting from GUI in tray).
Try to ping just after connection was set up.
The error that domain name can't be resolved is shown first 1-5 seconds.
Then all starts to work.
Expected behavior
If OpenVPN says that connection was successfully established then connection should be available immediatly.
Version information (please complete the following information):
- OS: Windows 11
- OpenVPN version: Tried 2.6.1 and 2.6.3.
Additional context
I saw the log and investigated the code. It looks like that there is no any tests on connectivity when wintun is used.
Contributor guide
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 files or tests are named. Start by reproducing the Windows 11 Wintun connection with ping <some_domain_name> immediately after setup, then trace the connection-established path and DNS behavior. Done means domain names resolve immediately after OpenVPN reports a successful connection, with a regression test covering the Wintun case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100