Bug 1219028 - dnscrypt takes a long time to activate the internet connection
Summary: dnscrypt takes a long time to activate the internet connection
Status: RESOLVED WORKSFORME
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Network (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-19 22:51 UTC by Eugene Popov
Modified: 2024-02-21 08:46 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
My dnscrypt-proxy.toml (1.66 KB, text/plain)
2024-01-19 22:51 UTC, Eugene Popov 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Eugene Popov 2024-01-19 22:51:34 UTC 
Created attachment 872036 [details]
My dnscrypt-proxy.toml

I'm on openSUSE Tumbleweed and I have a `dnscrypt-proxy` installed. Everything works fine, except for one: sometimes after rebooting it takes a long time to activate the internet connection (it may take up to 30 seconds). It also very rarely happens that the internet connection isn't activated at all and in this case even restarting the `dnscrypt-proxy` and `NetworkManager` services doesn't help, so I have to reboot my system. There's no such issue on Ubuntu and there I can use the internet immediately after logging in.
Comment 1 c unix 2024-02-09 20:13:27 UTC 
With the currently available information i can't see hints for an actionable bug in dnscrypt-proxy package.

With default configuration dnscrypt-proxy requires network connectivity, but other tools are used to setup or "activate" the network and provide connection to "internet".
Comment 2 Eugene Popov 2024-02-09 22:46:48 UTC 
What other information should I provide you with?

I don't see any errors in the logs. By "internet connection isn't activated" I mean that the internet connection is actually present (i.e. `ping 8.8.8.8' succeeded), but I can't resolve IP addresses (i.e. `ping google.com' failed).

My /etc/NetworkManager/NetworkManager.conf has the default contents except for this:

> [main]
> rc-manager=unmanaged

My /etc/resolv.conf looks like this:

> nameserver 127.0.0.1
> options edns0 single-request-reopen
Comment 3 c unix 2024-02-10 00:12:57 UTC 
Sorry, i can't help you with networkmanager related stuff.

One approach to debug the issue would be searching in logs and with systemd tools to find differences between the situation with working and not working dns resolution.

The various dnscrypt-proxy log files might be useful, status of involved systemd units, custom configurations changes, ...

Does this only happen with dnscrypt-proxy and not with other local resolvers?

If the network is up, dnscrypt-proxy receives a query but can't resolve it, i thought it should be possible to see this in its logs.

Is the attached file the complete configuration?
The default openSUSE one looks differently.
For example it offers more logging options that can be used to debug but are missing here.
Comment 4 Eugene Popov 2024-02-21 08:46:54 UTC 
It seems that switching to the default configuration fixed this issue for me. Thank you for your help.