Bug 251604 - security/openvpn: dns leak
Summary: security/openvpn: dns leak
Status: Closed Not Enough Information
Alias: None
Product: Base System
Classification: Unclassified
Component: misc (show other bugs)
Version: CURRENT
Hardware: Any Any
: --- Affects Only Me
Assignee: Matthias Andree
Depends on:
Reported: 2020-12-05 11:42 UTC by bsdashsan
Modified: 2020-12-26 16:15 UTC (History)
2 users (show)

See Also:
mandree: maintainer-feedback+

proof of the dns leak.... (345.96 KB, image/png)
2020-12-07 03:08 UTC, bsdashsan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description bsdashsan 2020-12-05 11:42:25 UTC
security/openvpn 2.5.0 
dns leak of ip address dns servers
cmd doas openvpn-client ...ovpn --auth-nocache
tried with 2 vpn provider protonvpn openvpn
leaked dns when doing initial connection
after awhile will be ok.
Comment 1 Matthias Andree freebsd_committer 2020-12-06 12:43:43 UTC
Hi bsdashsan,

"show me the bug". What exactly are you doing, and how do you see what leaks, and what part of it should not be leaking?

What does "after a[ ]while will be ok" mean?
Comment 2 bsdashsan 2020-12-07 03:08:12 UTC
Created attachment 220336 [details]
proof of the dns leak....
Comment 3 Matthias Andree freebsd_committer 2020-12-09 21:19:10 UTC
Comment on attachment 220336 [details]
proof of the dns leak....

Sorry, the issue you are reporting is still not obvious to me. 

It may be to you, but you need to make me able to explain your setup, the problem, and what you would have wanted instead, to the upstream OpenVPN developers.  I am currently unable.  Just imagine I sit in front of a blank sheet of paper and you start explaining to a stupid person.  I haven't been doing your job or setup for hours on end, so I am not in your shoes I'm afraid.

To go forward, could I ask you to please read through all of these two documents

and then provide the full information.