-
Notifications
You must be signed in to change notification settings - Fork 13
DNSCrypt support for V2Ray #129
Copy link
Copy link
Open
Labels
WindowsWindows Bugs, Features, Requests, EnhancementsWindows Bugs, Features, Requests, Enhancementsfeaturefeatures to be addedfeatures to be addedgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededlinuxissues relating to linux buildissues relating to linux buildosxissues relating to os x buildissues relating to os x build
Description
Activity
Metadata
Metadata
Labels
WindowsWindows Bugs, Features, Requests, EnhancementsWindows Bugs, Features, Requests, Enhancementsfeaturefeatures to be addedfeatures to be addedgood first issueGood for newcomersGood for newcomershelp wantedExtra attention is neededExtra attention is neededlinuxissues relating to linux buildissues relating to linux buildosxissues relating to os x buildissues relating to os x build
Currently all DNS and all traffic flow through the v2ray tunnel because of tun2socks. This is secure however may not be wanted as most node runners use google DNS or cloudflare DNS.
A way around this is to create a packet filter rule to send only DNS traffic through the localhost port 53 ONLY when DNscrypt is enabled.
On MacOS this can be achieved by creating a pf.conf file and reading it with the MacOS pfctl command as such
Windows & Linux is still TBD. Will update when testing is completed.