You are not logged in.

Pages: 1

#1 2019-11-27 17:20:14

ivo-a22
Member
Registered: 2018-11-26
Posts: 6

[Solved] Systemd-resolved problem? Cannot ping, connect to network

Hello guys,

This is my first post on this forum so firstly, I want to say hello to everybody.

I ' ve been looking and searching forum to solve my problem ( e.g https://github.com/systemd/systemd/issues/11102 ) but unfortunately all of it didn't work for me.

My problem: I  turned computer on. Automatically connected to my home wi-fi. Then I entered some websites. And after 3-5 minutes ( sometimes longer ) I cannot enter all of websites. I cannot ping servers e.g google.com. Like there isn't connection but my network is still up and connection is on. Please help me to solve this problem. It is really anoing.

/etc/systemd/resolved.conf

 
[Resolve]
#DNS=8.8.8.8 8.8.4.4
#FallbackDNS=1.1.1.1 9.9.9.10 8.8.8.8 2606:4700:4700::1111 2620:fe::10 2001:4860:4860::8888
#Domains=
#LLMNR=yes
#MulticastDNS=yes
DNSSEC=no
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes

cat /etc/systemd/network/25-wireless.network

[Match]
Name=wlan0

[Network]
DHCP=ipv4
DNSSEC=false

ip a

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0f1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000
    link/ether 98:28:a6:13:10:7f brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 70:c9:4e:bf:51:e5 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.66/24 brd 192.168.0.255 scope global dynamic wlan0
       valid_lft 3078sec preferred_lft 3078sec
    inet6 2a02:a311:c344:9a80:72c9:4eff:febf:51e5/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 1005020sec preferred_lft 400220sec
    inet6 fe80::72c9:4eff:febf:51e5/64 scope link 
       valid_lft forever preferred_lft forever

ip r 

default via 192.168.0.1 dev wlan0 proto dhcp src 192.168.0.66 metric 1024 
192.168.0.0/24 dev wlan0 proto kernel scope link src 192.168.0.66 
192.168.0.1 dev wlan0 proto dhcp scope link src 192.168.0.66 metric 1024

systemctl status systemd-resolved

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-11-27 16:31:28 CET; 1h 40min ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 479 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 14.4M
   CGroup: /system.slice/systemd-resolved.service
           └─479 /usr/lib/systemd/systemd-resolved

Nov 27 18:08:59 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2::53.
Nov 27 18:08:59 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2::53.
Nov 27 18:09:02 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:09:02 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:09:05 harbor systemd-resolved[479]: Failed to send hostname reply: Invalid argument
Nov 27 18:09:08 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:09:08 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2::53.
Nov 27 18:09:08 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2::53.
Nov 27 18:09:11 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:09:14 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2::53.

systemctl status systemd-networkd

● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-11-27 16:31:20 CET; 1h 42min ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 377 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 3.0M
   CGroup: /system.slice/systemd-networkd.service
           └─377 /usr/lib/systemd/systemd-networkd

Nov 27 16:31:20 harbor systemd-networkd[377]: Enumeration completed
Nov 27 16:31:20 harbor systemd[1]: Started Network Service.
Nov 27 16:31:20 harbor systemd-networkd[377]: enp2s0f1: Interface name change detected, enp2s0f1 has been renamed to eth0.
Nov 27 16:31:20 harbor systemd-networkd[377]: eth0: Interface name change detected, eth0 has been renamed to enp2s0f1.
Nov 27 16:31:22 harbor systemd-networkd[377]: wlan0: found matching network '/etc/systemd/network/25-wireless.network', based on potentially unpredictable ifname
Nov 27 16:31:22 harbor systemd-networkd[377]: wlan0: IPv6 successfully enabled
Nov 27 16:31:29 harbor systemd-networkd[377]: wlan0: IPv6 successfully enabled
Nov 27 16:31:29 harbor systemd-networkd[377]: wlan0: Gained carrier
Nov 27 16:31:29 harbor systemd-networkd[377]: wlan0: DHCPv4 address 192.168.0.66/24 via 192.168.0.1
Nov 27 16:31:32 harbor systemd-networkd[377]: wlan0: Gained IPv6LL

resolvectl

Global
       LLMNR setting: yes
MulticastDNS setting: yes
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
  Current DNS Server: 2001:730:3ed2:1000::53
         DNS Servers: 192.168.0.1
                      2001:730:3ed2::53
                      2001:730:3ed2:1000::53
Fallback DNS Servers: 1.1.1.1
                      9.9.9.10
                      8.8.8.8
                      2606:4700:4700::1111
                      2620:fe::10
                      2001:4860:4860::8888
          DNS Domain: home
          DNSSEC NTA: 10.in-addr.arpa
                      16.172.in-addr.arpa
                      168.192.in-addr.arpa
                      17.172.in-addr.arpa
                      18.172.in-addr.arpa
                      19.172.in-addr.arpa
                      20.172.in-addr.arpa
                      21.172.in-addr.arpa
                      22.172.in-addr.arpa
                      23.172.in-addr.arpa
                      24.172.in-addr.arpa
                      25.172.in-addr.arpa
                      26.172.in-addr.arpa
                      27.172.in-addr.arpa
                      28.172.in-addr.arpa
                      29.172.in-addr.arpa
                      30.172.in-addr.arpa
                      31.172.in-addr.arpa
                      corp
                      d.f.ip6.arpa
                      home
                      internal
                      intranet
                      lan
                      local
                      private
                      test

Link 4 (wlan0)
      Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
DefaultRoute setting: yes
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
  Current DNS Server: 192.168.0.1
         DNS Servers: 192.168.0.1
                      2001:730:3ed2::53
                      2001:730:3ed2:1000::53

Link 2 (enp2s0f1)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

This is what I have after loosing connection : 

ivo@harbor ~ % journalctl | tail                                                                                                                                                          [0]
Nov 27 18:23:44 harbor kernel: wlan0: associated
Nov 27 18:23:44 harbor systemd-networkd[377]: wlan0: Gained carrier
Nov 27 18:23:44 harbor systemd-timesyncd[480]: Network configuration changed, trying to establish connection.
Nov 27 18:23:45 harbor systemd-timesyncd[480]: Network configuration changed, trying to establish connection.
Nov 27 18:23:45 harbor systemd-networkd[377]: wlan0: DHCPv4 address 192.168.0.66/24 via 192.168.0.1
Nov 27 18:23:45 harbor systemd-timesyncd[480]: Network configuration changed, trying to establish connection.
Nov 27 18:23:45 harbor systemd-timesyncd[480]: Network configuration changed, trying to establish connection.
Nov 27 18:23:46 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
Nov 27 18:23:46 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
Nov 27 18:23:47 harbor systemd-timesyncd[480]: Network configuration changed, trying to establish connection.
ivo@harbor ~ % systemctl status systemd-resolved                                                                                                                                          [0]
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-11-27 16:31:28 CET; 1h 52min ago
     Docs: man:systemd-resolved.service(8)
           https://www.freedesktop.org/wiki/Software/systemd/resolved
           https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
           https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 479 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 14.5M
   CGroup: /system.slice/systemd-resolved.service
           └─479 /usr/lib/systemd/systemd-resolved

Nov 27 18:22:13 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:22:28 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:22:43 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:22:49 harbor systemd-resolved[479]: Failed to send hostname reply: Invalid argument
Nov 27 18:22:54 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:23:01 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:23:08 harbor systemd-resolved[479]: Using degraded feature set (TCP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:23:17 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 2001:730:3ed2:1000::53.
Nov 27 18:23:46 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 192.168.0.1.
Nov 27 18:23:46 harbor systemd-resolved[479]: Using degraded feature set (UDP) for DNS server 192.168.0.1.


I am using systemd-networkd with iwd . I was trying to changing DNSSEC values but it doesn't work. Have I something wrong in configuration files ?

Best Regards
Ivo

Last edited by ivo-a22 (2019-11-29 02:49:17)

Offline

#2 2019-11-28 16:45:55

ivo-a22
Member
Registered: 2018-11-26
Posts: 6

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

Maybe some tips only ? I can do it by myself but I don't know where to start

Offline

#3 2019-11-28 17:38:45

JackieCui
Member
Registered: 2019-11-15
Posts: 4

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

hi， this is my first post too. Hope I can help


First of all, are you sure your network is OK? You can test it by directly ping some ip first to avoid DNS. May be start with 192.168.0.1, and then
8.8.8.8

If network is good, maybe you can try to disable ipv6.
It caused me some trouble before.

Offline

#4 2019-11-28 17:43:07

JackieCui
Member
Registered: 2019-11-15
Posts: 4

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

Also, you can test dns server using host/nslookup/dig command, which is contained in bind-tools package.

eg: host google.com 192.168.0.1

Offline

#5 2019-11-29 01:42:46

ivo-a22
Member
Registered: 2018-11-26
Posts: 6

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

Okay , I have inspected what causes the problem. Everything is working fine while resolvectl is using 192.168.0.1 as a DNS server. When DNS server has changed to 2001:730:3ed2::53 or 2001:730:3ed2:1000::53 the connection is lost. Those servers are stored in etc/resolv.conf , can I use only 192.168.0.1 server in etc/resolv.conf ? And there will be no trouble about it ? Or should I change /etc/systemd/resolved.conf ? What differs those two configuration files ? Can smb explain this ?

P.s I have changed /etc/resolv.conf  and used fixed dns 192.168.0.1 now it works fine , for those who want to know difference between modes of resolver I suggest : https://unix.stackexchange.com/question … a585abbf85

Last edited by ivo-a22 (2019-11-29 02:47:15)

Offline

#6 2019-11-29 04:08:32

JackieCui
Member
Registered: 2019-11-15
Posts: 4

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

Yes, it's ipv6 again.

When I had this problem, I just used sysctl to disable ipv6, and everything worked after that.

I don't think it's a good idea to modify /etc/resolv.conf directly. Maybe you can search for some information about ipv6 and ipv4 if you really need ipv6

Offline

#7 2019-11-29 04:14:33

JackieCui
Member
Registered: 2019-11-15
Posts: 4

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

Maybe start with https://wiki.archlinux.org/index.php/IP … _over_IPv6

Offline

#8 2019-12-01 21:46:54

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 20,346

Re: [Solved] Systemd-resolved problem? Cannot ping, connect to network

JackieCui wrote:

Yes, it's ipv6 again.

When I had this problem, I just used sysctl to disable ipv6, and everything worked after that.

I don't think it's a good idea to modify /etc/resolv.conf directly. Maybe you can search for some information about ipv6 and ipv4 if you really need ipv6

Okay, but...
https://www.theregister.co.uk/2019/11/2 … sses_gone/

I suggest it is time to start to figure out issues with IPv6 rather than hope it just goes away.

Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

Pages: 1

Board footer

Powered by FluxBB