[Bug 1219028] New: dnscrypt takes a long time to activate the internet connection
https://bugzilla.suse.com/show_bug.cgi?id=1219028 Bug ID: 1219028 Summary: dnscrypt takes a long time to activate the internet connection Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Network Assignee: screening-team-bugs@suse.de Reporter: popov895@ukr.net QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- Created attachment 872036 --> https://bugzilla.suse.com/attachment.cgi?id=872036&action=edit 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219028 Eugene Popov <popov895@ukr.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |popov895@ukr.net -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219028 https://bugzilla.suse.com/show_bug.cgi?id=1219028#c1 c unix <cunix@mail.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|cunix@mail.de |screening-team-bugs@suse.de CC| |cunix@mail.de --- Comment #1 from c unix <cunix@mail.de> --- 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". -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219028 https://bugzilla.suse.com/show_bug.cgi?id=1219028#c3 --- Comment #3 from c unix <cunix@mail.de> --- 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. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1219028 https://bugzilla.suse.com/show_bug.cgi?id=1219028#c4 Eugene Popov <popov895@ukr.net> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |WORKSFORME Status|NEW |RESOLVED --- Comment #4 from Eugene Popov <popov895@ukr.net> --- It seems that switching to the default configuration fixed this issue for me. Thank you for your help. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com