Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not working with VPN #221

Closed
forgedhallpass opened this issue Jul 12, 2022 · 3 comments · Fixed by #264
Closed

Not working with VPN #221

forgedhallpass opened this issue Jul 12, 2022 · 3 comments · Fixed by #264
Assignees
Labels
documentation Improvements or additions to documentation Priority: Medium This issue may be useful, and needs some attention. Status: Completed Nothing further to be done with this issue. Awaiting to be closed.
Milestone

Comments

@forgedhallpass
Copy link
Contributor

The -v and/or -raw/-debug, -stats flags should indicate that there is a problem.
image

@forgedhallpass forgedhallpass added Priority: Medium This issue may be useful, and needs some attention. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. labels Jul 12, 2022
@Mzack9999 Mzack9999 self-assigned this Aug 3, 2022
@Mzack9999 Mzack9999 added the Status: In Progress This issue is being worked on, and has someone assigned. label Aug 3, 2022
@Mzack9999
Copy link
Member

From their website:

If you are using the Mullvad VPN app, you are automatically safe from DNS leaks. All of your DNS requests get rerouted to our own non-logging DNS resolver instead of to your ISP or a public DNS provider.

I suppose that this network filtering and the potentially high rate of DNS requests might cause malfunctioning.
I would propose the following:

  • Updating the docs warning users of possible packet loss while using DNS UDP with VPNs
  • Adding a new stats Error/Packet Loss counting those packets that didn't get any network reply

@forgedhallpass Would this satisfy your request?

@Mzack9999 Mzack9999 added Status: On Hold Similar to blocked, but is assigned to someone Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all. and removed Status: In Progress This issue is being worked on, and has someone assigned. labels Aug 3, 2022
@forgedhallpass
Copy link
Contributor Author

@Mzack9999 yes, I think that would be helpful.

@forgedhallpass forgedhallpass added documentation Improvements or additions to documentation and removed Status: On Hold Similar to blocked, but is assigned to someone Type: Question A query or seeking clarification on parts of the spec. Probably doesn't need the attention of all. Type: Bug Inconsistencies or issues which will cause an issue or problem for users or implementors. labels Aug 25, 2022
@Mzack9999
Copy link
Member

Mzack9999 commented Sep 26, 2022

Todo:

  • Update README.md: using VPN might cause network packet losses
  • Consider adding a packet loss/packet without answer metric (optional) (not planned)

@Mzack9999 Mzack9999 linked a pull request Nov 8, 2022 that will close this issue
@ehsandeep ehsandeep added the Status: Completed Nothing further to be done with this issue. Awaiting to be closed. label Nov 17, 2022
@Mzack9999 Mzack9999 changed the title Not working with Mullvad VPN Not working with VPN Nov 17, 2022
@ehsandeep ehsandeep added this to the dnsx v1.1.2 milestone Jan 6, 2023
noctisatrae added a commit to noctisatrae/dnsx that referenced this issue Aug 28, 2024
I had the same problem using dnsx as in projectdiscovery#221 and I successfully found a way around Mullvad's limitations. Wanted to share my solution.
ehsandeep pushed a commit that referenced this issue Aug 29, 2024
* A guide explaining how to use dnsx with Mullvad

I had the same problem using dnsx as in #221 and I successfully found a way around Mullvad's limitations. Wanted to share my solution.

* Add the solution to the README.md
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation Priority: Medium This issue may be useful, and needs some attention. Status: Completed Nothing further to be done with this issue. Awaiting to be closed.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants