Skip to main content ↑ ↓
Topic: DNSCrypt for s6 (Read 1877 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

Re: DNSCrypt for s6

Reply #30 –
There's a folder called dnscrypt-proxy which contain 3 readable files but they're all empty

Re: DNSCrypt for s6

Reply #32 –
At this point you're just better off making the file immutable so you can see if dnscrypt-proxy works at all, execute chattr +i /etc/resolv.conf

Quote from: Piere – on
No need to be rude, the command did nothing.

As in what? what output did it give?

Re: DNSCrypt for s6

Reply #33 –
It gave no output.

The same goes for  chattr +i /etc/resolv.conf. I tried running it as sudo too with no result.





Re: DNSCrypt for s6

Reply #34 –
On my system
when I run : sudo dnscrypt-proxy -config /etc/dnscrypt-proxy/dnscrypt-proxy.toml
output
Code: [Select]
[2022-10-26 21:19:33] [NOTICE] dnscrypt-proxy 2.1.2
[2022-10-26 21:19:33] [NOTICE] Network connectivity detected
[2022-10-26 21:19:33] [NOTICE] Now listening to 127.0.0.1:53 [UDP]
[2022-10-26 21:19:33] [NOTICE] Now listening to 127.0.0.1:53 [TCP]
[2022-10-26 21:19:33] [NOTICE] Now listening to [::1]:53 [UDP]
[2022-10-26 21:19:33] [NOTICE] Now listening to [::1]:53 [TCP]
[2022-10-26 21:19:35] [WARNING] /var/cache/dnscrypt-proxy/public-resolvers.md: open /var/cache/dnscrypt-proxy/sf-ks4l7qiijhbbmspo.tmp: no such file or directory
[2022-10-26 21:19:35] [NOTICE] Source [public-resolvers] loaded
[2022-10-26 21:19:35] [NOTICE] Firefox workaround initialized
[2022-10-26 21:19:41] [NOTICE] [scaleway-fr] TIMEOUT
[2022-10-26 21:19:46] [NOTICE] [resolver4.dns.openinternet.io] TIMEOUT
[2022-10-26 21:19:52] [NOTICE] [quad9-dnscrypt-ip4-nofilter-pri] TIMEOUT
[2022-10-26 21:19:54] [NOTICE] [doh.ffmuc.net] OK (DoH) - rtt: 610ms
[2022-10-26 21:19:56] [NOTICE] [uncensoreddns-ipv4] OK (DoH) - rtt: 409ms
[2022-10-26 21:19:59] [NOTICE] [nextdns-ultralow] OK (DoH) - rtt: 283ms
[2022-10-26 21:20:05] [NOTICE] [dnscrypt.ca-2] TIMEOUT
[2022-10-26 21:20:06] [NOTICE] [sby-doh-limotelu] OK (DoH) - rtt: 407ms
[2022-10-26 21:20:12] [NOTICE] [saldns01-conoha-ipv4] TIMEOUT
[2022-10-26 21:20:14] [NOTICE] [ams-doh-nl] OK (DoH) - rtt: 307ms
[2022-10-26 21:20:20] [NOTICE] [saldns03-conoha-ipv4] TIMEOUT
[2022-10-26 21:20:22] [NOTICE] [jp.tiar.app-doh] OK (DoH) - rtt: 270ms
[2022-10-26 21:20:23] [NOTICE] [dns.ryan-palmer] OK (DoH) - rtt: 204ms
[2022-10-26 21:20:23] [NOTICE] [quad9-doh-ip4-port443-nofilter-pri] OK (DoH) - rtt: 201ms
[2022-10-26 21:20:29] [NOTICE] [dnscrypt.be] TIMEOUT
[2022-10-26 21:20:34] [NOTICE] [altername] TIMEOUT
[2022-10-26 21:20:35] [NOTICE] [quad9-doh-ip4-port5053-nofilter-pri] OK (DoH) - rtt: 162ms
[2022-10-26 21:20:37] [NOTICE] [dnscrypt.ca-2-doh] OK (DoH) - rtt: 309ms
[2022-10-26 21:20:43] [NOTICE] [plan9dns-fl] TIMEOUT
[2022-10-26 21:20:43] [NOTICE] [bortzmeyer] OK (DoH) - rtt: 208ms

cat /etc/resolv.conf
Code: [Select]
# Generated by NetworkManager
nameserver 192.168.1.1
Create problems which don't have solution

Re: DNSCrypt for s6

Reply #35 –
I think I might've found the reason why my resolv.conf changes, I had connman still installed after I installed NetworkManager. Issue now is that I can't connect to the internet since I've removed connman.

The command you posted above still doesn't show anything for me for some reason.

Re: DNSCrypt for s6

Reply #36 –
>The same goes for  chattr +i /etc/resolv.conf. I tried running it as sudo too with no result.

That's natural, you can verify that the immutable flag has been set using lsattr(1)

Re: DNSCrypt for s6

Reply #37 –
I changed it back to -i earlier so I could edit resolv.conf again to see if something I did worked. Now i'm stuck with "fatal: networkmanager is not a recognized identifier in run/s6-db/state" when I try to run networkmanager instead of connman. Btw yes I have the networkmanager s6 script.

Re: DNSCrypt for s6

Reply #38 –
there is no need to remove connman pkg , connman and networkmanager should not running at same time
Create problems which don't have solution

Re: DNSCrypt for s6

Reply #39 –
Connman was altering my resolv.conf which is the reason why I removed it.

Anyone got any ideas how to run networkmanager through s6 without the  "fatal: networkmanager is not a recognized identifier in run/s6-db/state" message?

Re: DNSCrypt for s6

Reply #40 –
update s6 db
Create problems which don't have solution

Re: DNSCrypt for s6

Reply #41 –
That's what I did right after I installed the s6 script for it earlier, I also made it a default service.

Re: DNSCrypt for s6

Reply #42 –
Figured out the internet issue I had to rename the service from networkmanager to NetworkManager

Re: DNSCrypt for s6

Reply #43 –
Conman was the issue. I've fixed my DNS leak and my connectivity issue. Thanks for helping me everyone for the past couple of days.