You are not logged in.

Pages: 1

#1 2019-04-23 18:46:02

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 28

[SOLVED] Networking messed up: cannot ping domain names

Hello,

I have been experiencing some issues with my networking since the installation and initial configuration of my arch box.
I can't ping any domain names, but I can normally ping IPs. My internet is working, but somewhat slower than normally.
The system boot-up time has significantly increased.

I cannot have functioning VPN connected up for some reason. The VPN is working flawlessly on my girlfriend's Manjaro box as well as on my OpenBSD system.

I wrote on a couple of different forums but no luck. I feel the solution should be simple but I haven't gotten it yet and would greatly benefit of some assistance
since I am no networking expert.


$ ping google.com

PING google.com(2a00:1450:400b:c01::8a (2a00:1450:400b:c01::8a)) 56 data bytes
From pool-ipv6-pd.agg2.kln.lmk-mlw.eircom.net (2001:bb6:340b:1858::1): icmp_seq=1 Destination unreachable: Address unreachable


$ ping 8.8.8.8

PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=120 time=11.6 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=120 time=12.3 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=120 time=11.8 ms


$ [ ping -I enp0s25 fe80::1

ping6: Warning: source address might be selected on device other than enp0s25.
PING fe80::1(fe80::1) from :: enp0s25: 56 data bytes
64 bytes from fe80::1%enp0s25: icmp_seq=1 ttl=64 time=0.623 ms
64 bytes from fe80::1%enp0s25: icmp_seq=2 ttl=64 time=0.474 ms
64 bytes from fe80::1%enp0s25: icmp_seq=3 ttl=64 time=0.517 ms
64 bytes from fe80::1%enp0s25: icmp_seq=4 ttl=64 time=0.486 ms



$ ip link

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether a0:b3:cc:29:9e:4e brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 8c:70:5a:aa:04:ca brd ff:ff:ff:ff:ff:ff


$ ip addr

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: enp0s25: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether a0:b3:cc:29:9e:4e brd ff:ff:ff:ff:ff:ff
3: wlo1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 8c:70:5a:aa:04:ca brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.5/24 brd 192.168.1.255 scope global dynamic wlo1
       valid_lft 258744sec preferred_lft 258744sec
    inet6 2001:bb6:340b:1858:8e70:5aff:feaa:4ca/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 6746sec preferred_lft 3146sec
    inet6 2001:bb6:340b:1858:8f6:e5e2:f2bd:23ce/64 scope global dynamic noprefixroute 
       valid_lft 7133sec preferred_lft 3533sec
    inet6 fe80::14f6:5c16:c36b:cfb8/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever


$ ip route

default via 192.168.1.254 dev wlo1 proto dhcp metric 600 
default via 192.168.1.254 dev wlo1 proto dhcp src 192.168.1.5 metric 1024 
192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.5 
192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.5 metric 600 
192.168.1.254 dev wlo1 proto dhcp scope link src 192.168.1.5 metric 1024


$ ip neigh show

192.168.1.4 dev enp0s25 lladdr b0:2a:43:00:44:09 REACHABLE
192.168.1.254 dev enp0s25 lladdr 80:7d:14:63:79:a0 REACHABLE
2001:bb6:340b:1858::1 dev enp0s25 lladdr 80:7d:14:63:79:a0 router STALE
fe80::1 dev enp0s25 lladdr 80:7d:14:63:79:a0 router REACHABLE


$ nmcli c show Wired\ connection\ 1

connection.id:                          Wired connection 1
connection.uuid:                        40921302-fd99-3ec8-8656-99f54e4>
connection.stable-id:                   --
connection.type:                        802-3-ethernet
connection.interface-name:              --
connection.autoconnect:                 yes
connection.autoconnect-priority:        -100
connection.autoconnect-retries:         -1 (default)
connection.multi-connect:               0 (default)
connection.auth-retries:                -1
connection.timestamp:                   1556039908
connection.read-only:                   no
connection.permissions:                 --
connection.zone:                        --
connection.master:                      --
connection.slave-type:                  --
connection.autoconnect-slaves:          -1 (default)
connection.secondaries:                 --
connection.gateway-ping-timeout:        0
connection.metered:                     unknown
connection.lldp:                        default
connection.mdns:                        -1 (default)
connection.llmnr:                       -1 (default)
802-3-ethernet.port:                    --
802-3-ethernet.speed:                   0
802-3-ethernet.duplex:                  --
802-3-ethernet.auto-negotiate:          yes
802-3-ethernet.mac-address:             A0:B3:CC:29:9E:4E
802-3-ethernet.cloned-mac-address:      --
802-3-ethernet.generate-mac-address-mask:--
802-3-ethernet.mac-address-blacklist:   --


$ journalctl -u NetworkManager.service --since -15m

- Logs begin at Wed 2019-04-10 19:06:58 IST, end at Tue 2019-04-23 19:17:40 IST. --
Apr 23 19:03:16 t111nemesis NetworkManager[567]: <warn>  [1556042596.3605] dhcp6 (wlo1): request timed out
Apr 23 19:03:16 t111nemesis NetworkManager[567]: <info>  [1556042596.3607] dhcp6 (wlo1): state changed unknown -> timeout
Apr 23 19:03:16 t111nemesis NetworkManager[567]: <info>  [1556042596.3608] dhcp6 (wlo1): canceled DHCP transaction
Apr 23 19:03:16 t111nemesis NetworkManager[567]: <info>  [1556042596.3609] dhcp6 (wlo1): state changed timeout -> done
Apr 23 19:12:38 t111nemesis NetworkManager[567]: <info>  [1556043158.1914] audit: op="statistics" arg="refresh-rate-ms" pid=805 uid=1000 result=">
Apr 23 19:12:39 t111nemesis NetworkManager[567]: <info>  [1556043159.5232] audit: op="statistics" arg="refresh-rate-ms" pid=805 uid=1000 result="


$ sudo lshw -C network

  *-network                 
       description: Ethernet interface
       product: 82579LM Gigabit Network Connection (Lewisville)
       vendor: Intel Corporation
       physical id: 19
       bus info: pci@0000:00:19.0
       logical name: enp0s25
       version: 04
       serial: a0:b3:cc:29:9e:4e
       capacity: 1Gbit/s
       width: 32 bits
       clock: 33MHz
       capabilities: pm msi bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
       configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.13-4 latency=0 link=no multicast=yes port=twisted pair
       resources: irq:39 memory:d4800000-d481ffff memory:d482a000-d482afff ioport:4060(size=32)
  *-network
       description: Wireless interface
       product: Centrino Advanced-N 6205 [Taylor Peak]
       vendor: Intel Corporation
       physical id: 0
       bus info: pci@0000:24:00.0
       logical name: wlo1
       version: 34
       serial: 8c:70:5a:aa:04:ca
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=5.0.8-arch1-1-ARCH firmware=18.168.6.1 ip=192.168.1.5 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: irq:41 memory:d4500000-d4501fff


$ cat /etc/nsswitch.conf

passwd: files mymachines systemd
group: files mymachines systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files


$ cat /etc/hosts

127.0.0.1       localhost
127.0.1.1       t111nemesis
::1             localhost ip6-localhost ip6-loopback
ff00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts


$ cat /etc/resolvconf.conf

resolv_conf=/etc/resolv.conf
# If you run a local name server, you should uncomment the below line and
# configure your subscribers configuration files below.
#name_servers=127.0.0.1


$ cat /etc/resolv.conf

# Generated by NetworkManager
search home
nameserver 192.168.1.254
nameserver fe80::1%wlo1


$ nslookup google.com

Server:         192.168.1.254
Address:        192.168.1.254#53

Non-authoritative answer:
Name:   google.com
Address: 74.125.193.113
Name:   google.com
Address: 74.125.193.138
Name:   google.com
Address: 74.125.193.139
Name:   google.com
Address: 74.125.193.102
Name:   google.com
Address: 74.125.193.101
Name:   google.com
Address: 74.125.193.100
Name:   google.com
Address: 2a00:1450:400b:c01::8a


$ route -v

~ [ route -v                                                  ] 7:30 PM
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         _gateway        0.0.0.0         UG    600    0        0 wlo1
default         _gateway        0.0.0.0         UG    1024   0        0 wlo1
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlo1
192.168.1.0     0.0.0.0         255.255.255.0   U     600    0        0 wlo1
_gateway        0.0.0.0         255.255.255.255 UH    1024   0        0 wlo1


$ resolvectl status

Failed to get global data: Unit dbus-org.freedesktop.resolve1.service not found.


$  resolvectl query archlinux.org

archlinux.org: resolve call failed: Unit dbus-org.freedesktop.resolve1.service not found.


$ netstat -r

Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
default         _gateway        0.0.0.0         UG        0 0          0 enp0s25
default         _gateway        0.0.0.0         UG        0 0          0 enp0s25
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 enp0s25
192.168.1.0     0.0.0.0         255.255.255.0   U         0 0          0 enp0s25
_gateway        0.0.0.0         255.255.255.255 UH        0 0          0 enp0s25



$ ip -6 route

::1 dev lo proto kernel metric 256 pref medium
2001:bb6:340b:1858::/64 dev enp0s25 proto ra metric 100 pref medium
2001:bb6:340b:1858::/64 dev enp0s25 proto ra metric 1024 expires 6849sec pref medium
fe80::/64 dev enp0s25 proto kernel metric 100 pref medium
default via fe80::1 dev enp0s25 proto ra metric 1024 expires 1449sec mtu 1500 pref high
default via fe80::1 dev enp0s25 proto ra metric 20100 pref high


$ traceroute ipv6.google.com

traceroute to ipv6.google.com (2a00:1450:400b:c01::66), 30 hops max, 80 byte packets
 1  pool-ipv6-pd.agg2.kln.lmk-mlw.eircom.net (2001:bb6:340b:1858::1)  0.534 ms  0.838 ms  1.044 ms
 2  pool-ipv6-pd.agg2.kln.lmk-mlw.eircom.net (2001:bb6:340b:1858::1)  2999.499 ms !H  2999.540 ms !H  2999.683 ms !H


$ traceroute ipv4.google.com

traceroute to ipv4.google.com (74.125.193.138), 30 hops max, 60 byte packets
 1  _gateway (192.168.1.254)  0.559 ms  0.753 ms  0.901 ms
 2  95-44-112-1-dynamic.agg2.kln.lmk-mlw.eircom.net (95.44.112.1)  10.318 ms  12.512 ms  14.404 ms
 3  lag-22.pe1.mlw.lmk-mlw.eircom.net (86.43.10.245)  7.492 ms  7.567 ms  7.632 ms
 4  lag-107-coreb-dbn-pe1-mlw.coreb.dbn.core.eircom.net (86.43.9.238)  10.892 ms  11.292 ms  11.463 ms
 5  eth-trunk1.hcore1.dbn.core.eircom.net (83.174.185.15)  15.018 ms  15.082 ms  15.127 ms
 6  lag-60-br1-6cr-hcore1-dbn.br1.6cr.border.eircom.net (86.43.12.213)  13.616 ms  13.706 ms  13.726 ms
 7  72.14.205.72 (72.14.205.72)  11.869 ms  9.417 ms  9.590 ms
 8  74.125.243.226 (74.125.243.226)  12.835 ms 74.125.244.2 (74.125.244.2)  11.256 ms 74.125.243.226 (74.125.243.226)  11.020 ms
 9  72.14.235.189 (72.14.235.189)  10.140 ms  10.062 ms 216.239.47.213 (216.239.47.213)  13.035 ms
10  * * *
11  * * *
12  * * *
13  * * *
14  * * *
15  * * *
16  * * ig-in-f138.1e100.net (74.125.193.138)  12.301 ms

My VPN is not working either, I am getting this error in my logs: "Error: Nexthop has invalid gateway.ERROR: Linux route add command failed: external program exited with error status: 2
/sbin/ip route add 128.0.0.0/1 via 10.142.0.125"


$ expressvpn diagnostics

Client Version: 2.1.0
Client Shared Version: v1.5.2
OS Name: linux
OS Version: Arch Linux 
Internal diagnostics data:
D01: 1378, OK
D02: 1378, OK
D03: 1377
D04: 1377, OK
D05: 1377, OK
D06: 1377
D07: 1377, OK
D08: 1377, OK
D09: 1377, OK
D10: 1377, OK
D11: 1377, OK
D12: 7, 53
D13: https://www.hgm2akdl.net
D14: UK - East London
D15: auto


==============================================

Connecting to UK - East London, ip: 24.23.152.133x, protocol: udp

Sat Apr 13 22:37:56 2019 WARNING: --keysize is DEPRECATED and will be removed in OpenVPN 2.6
Sat Apr 13 22:37:56 2019 OpenVPN 2.4.7 x86_64-unknown-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [MH/PKTINFO] [AEAD] built on Feb 28 2019
Sat Apr 13 22:37:56 2019 library versions: OpenSSL 1.1.1b  26 Feb 2019, LZO 2.10
Sat Apr 13 22:37:56 2019 MANAGEMENT: TCP Socket listening on [AF_INET]127.0.0.1:42193
Sat Apr 13 22:37:56 2019 WARNING: --ns-cert-type is DEPRECATED.  Use --remote-cert-tls instead.
Sat Apr 13 22:37:56 2019 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts
Sat Apr 13 22:37:56 2019 Outgoing Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sat Apr 13 22:37:56 2019 Incoming Control Channel Authentication: Using 256 bit message hash 'SHA256' for HMAC authentication
Sat Apr 13 22:37:57 2019 TCP/UDP: Preserving recently used remote address: [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:57 2019 Socket Buffers: R=[212992->425984] S=[212992->425984]
Sat Apr 13 22:37:57 2019 UDP link local: (not bound)
Sat Apr 13 22:37:57 2019 UDP link remote: [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:57 2019 TLS: Initial packet from [AF_INET]24.23.152.133:43218, sid=dec104d3 aa4c7607
Sat Apr 13 22:37:57 2019 WARNING: this configuration may cache passwords in memory -- use the auth-nocache option to prevent this
Sat Apr 13 22:37:57 2019 VERIFY OK: depth=1, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=ExpressVPN CA, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 VERIFY OK: nsCertType=SERVER
Sat Apr 13 22:37:57 2019 VERIFY X509NAME OK: C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3636-0a, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 VERIFY OK: depth=0, C=VG, ST=BVI, O=ExpressVPN, OU=ExpressVPN, CN=Server-3636-0a, emailAddress=support@expressvpn.com
Sat Apr 13 22:37:57 2019 Control Channel: TLSv1.2, cipher TLSv1.2 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Sat Apr 13 22:37:57 2019 [Server-3636-0a] Peer Connection Initiated with [AF_INET]24.23.152.133:43218
Sat Apr 13 22:37:58 2019 SENT CONTROL [Server-3636-0a]: 'PUSH_REQUEST' (status=1)
Sat Apr 13 22:37:58 2019 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1,dhcp-option DNS 10.142.0.1,route 10.142.0.1,topology net30,ping 10,ping-restart 60,ifconfig 10.142.0.126 10.142.0.125,peer-id 29,cipher AES-256-GCM'
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: timers and/or timeouts modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: --ifconfig/up options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: route options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: peer-id set
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: adjusting link_mtu to 1628
Sat Apr 13 22:37:58 2019 OPTIONS IMPORT: data channel crypto options modified
Sat Apr 13 22:37:58 2019 Data Channel: using negotiated cipher 'AES-256-GCM'
Sat Apr 13 22:37:58 2019 NCP: overriding user-set keysize with default
Sat Apr 13 22:37:58 2019 Outgoing Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Apr 13 22:37:58 2019 Incoming Data Channel: Cipher 'AES-256-GCM' initialized with 256 bit key
Sat Apr 13 22:37:58 2019 TUN/TAP device tun0 opened
Sat Apr 13 22:37:58 2019 TUN/TAP TX queue length set to 100
Sat Apr 13 22:37:58 2019 /sbin/ip link set dev tun0 up mtu 1500
Sat Apr 13 22:37:58 2019 /sbin/ip addr add dev tun0 local 10.142.0.126 peer 10.142.0.125
Sat Apr 13 22:37:58 2019 /usr/sbin/expressvpnd --update-resolv-conf tun0 1500 1556 10.142.0.126 10.142.0.125 init
dhcp-option DNS 10.142.0.1
Sat Apr 13 22:37:58 2019 /sbin/ip route add 24.23.152.133/32 via 192.168.1.254
Sat Apr 13 22:37:58 2019 /sbin/ip route add 0.0.0.0/1 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 /sbin/ip route add 128.0.0.0/1 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 /sbin/ip route add 10.142.0.1/32 via 10.142.0.125
Error: Nexthop has invalid gateway.
Sat Apr 13 22:37:58 2019 ERROR: Linux route add command failed: external program exited with error status: 2
Sat Apr 13 22:37:58 2019 Initialization Sequence Completed

Last edited by tlillenuit (2019-04-24 18:37:33)

Offline

#2 2019-04-23 20:11:59

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 28

Re: [SOLVED] Networking messed up: cannot ping domain names

UPDATE: systemd-resolved.service was disabled for some reason. I am not sure should it be disabled or not, but I tried enabling it. It didn't make any difference, except one additional error in the logs:

$ sudo systemctl status systemd-resolved.service

● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/usr/lib/systemd/system/systemd-resolved.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2019-04-23 21:06:01 IST; 5min 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: 464 (systemd-resolve)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 5.8M
   CGroup: /system.slice/systemd-resolved.service
           └─464 /usr/lib/systemd/systemd-resolved

Apr 23 21:06:01 t111nemesis systemd-resolved[464]: Positive Trust Anchors:
Apr 23 21:06:01 t111nemesis systemd-resolved[464]: . IN DS 19036 8 2 49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Apr 23 21:06:01 t111nemesis systemd-resolved[464]: . IN DS 20326 8 2 e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Apr 23 21:06:01 t111nemesis systemd-resolved[464]: Negative trust anchors: 10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172>
Apr 23 21:06:01 t111nemesis systemd-resolved[464]: Using system hostname 't111nemesis'.
Apr 23 21:06:01 t111nemesis systemd[1]: Started Network Name Resolution.
Apr 23 21:06:13 t111nemesis systemd-resolved[464]: Using degraded feature set (UDP) for DNS server 192.168.1.254.
Apr 23 21:06:13 t111nemesis systemd-resolved[464]: Server 192.168.1.254 does not support DNSSEC, downgrading to non-DNSSEC mode.
Apr 23 21:06:35 t111nemesis systemd-resolved[464]: Using degraded feature set (UDP) for DNS server 192.168.1.254.
Apr 23 21:06:35 t111nemesis systemd-resolved[464]: Server 192.168.1.254 does not support DNSSEC, downgrading to non-DNSSEC mode.

Offline

#3 2019-04-24 09:42:42

Lone_Wolf
Administrator
From: Netherlands, Europe
Registered: 2005-10-04
Posts: 13,342

Re: [SOLVED] Networking messed up: cannot ping domain names

systemd-resolved is only if systemd-networkd is managing your network settings.

https://wiki.archlinux.org/index.php/Ne … k_managers
Which of those tools are managing your network connections ?

N.B. you can also a dhcp client to manage things without using any of those tools, or setup things manually.

Disliking systemd intensely, but not satisfied with alternatives so focusing on taming systemd.

clean chroot building not flexible enough ?
Try clean chroot manager by graysky

Offline

#4 2019-04-24 14:57:11

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 28

Re: [SOLVED] Networking messed up: cannot ping domain names

Hm, seems like systemd-networkd and NetworkManager are both active. They must have been in a collision then? To be honest, I am really not sure which one was used primarily. Those two seem to confuse me a bit. Should I switch one of these off? Based on reviewing the etc files I've got, I think it might have been systemd-networkd.

My /etc/NetworkManager/NetworkManager.conf along with its respective subdirectories, is empty:

$ cat /etc/systemd/networkd.conf

[DHCP]
#DUIDType=vendor
#DUIDRawData=


$ cat /etc/systemd/resolved.conf

[Resolve]
#DNS=
#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=allow-downgrade
#DNSOverTLS=no
#Cache=yes
#DNSStubListener=yes
#ReadEtcHosts=yes


● NetworkManager.service - Network Manager
   Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
           └─NetworkManager-ovs.conf
   Active: active (running) since Wed 2019-04-24 15:30:06 IST; 9min ago
     Docs: man:NetworkManager(8)
 Main PID: 524 (NetworkManager)
    Tasks: 3 (limit: 4915)
   Memory: 19.8M
   CGroup: /system.slice/NetworkManager.service
           └─524 /usr/bin/NetworkManager --no-daemon

Apr 24 15:30:16 t111nemesis NetworkManager[524]: <warn>  [1556116216.4651] dns-sd-resolved[0x55efb7602510]: Failed: GDBus.Error:org>
Apr 24 15:30:16 t111nemesis NetworkManager[524]: <warn>  [1556116216.4652] dns-sd-resolved[0x55efb7602510]: Failed: GDBus.Error:org>
Apr 24 15:30:16 t111nemesis NetworkManager[524]: <warn>  [1556116216.4652] dns-sd-resolved[0x55efb7602510]: Failed: GDBus.Error:org>
Apr 24 15:30:16 t111nemesis NetworkManager[524]: <warn>  [1556116216.4652] dns-sd-resolved[0x55efb7602510]: Failed: GDBus.Error:org>
Apr 24 15:30:48 t111nemesis NetworkManager[524]: <info>  [1556116248.0446] manager: NetworkManager state is now CONNECTED_GLOBAL
Apr 24 15:31:00 t111nemesis NetworkManager[524]: <warn>  [1556116260.6115] dhcp6 (enp0s25): request timed out
Apr 24 15:31:00 t111nemesis NetworkManager[524]: <info>  [1556116260.6116] dhcp6 (enp0s25): state changed unknown -> timeout
Apr 24 15:31:00 t111nemesis NetworkManager[524]: <info>  [1556116260.6118] dhcp6 (enp0s25): canceled DHCP transaction
Apr 24 15:31:00 t111nemesis NetworkManager[524]: <info>  [1556116260.6118] dhcp6 (enp0s25): state changed timeout -> done
Apr 24 15:31:08 t111nemesis NetworkManager[524]: <info>  [1556116268.1450] agent-manager: req[0x55efb76d54f0, :1.74/org.kde.plasma.>

~ [ sudo systemctl status systemd-networkd.service                                                                        ] 3:48 PM
● systemd-networkd.service - Network Service
   Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-04-24 15:30:06 IST; 18min ago
     Docs: man:systemd-networkd.service(8)
 Main PID: 330 (systemd-network)
   Status: "Processing requests..."
    Tasks: 1 (limit: 4915)
   Memory: 2.7M
   CGroup: /system.slice/systemd-networkd.service
           └─330 /usr/lib/systemd/systemd-networkd

Apr 24 15:30:06 t111nemesis systemd-networkd[330]: eth0: Interface name change detected, eth0 has been renamed to enp0s25.
Apr 24 15:30:07 t111nemesis systemd-networkd[330]: enp0s25: Could not bring up interface: Invalid argument
Apr 24 15:30:07 t111nemesis systemd-networkd[330]: wlan0: Interface name change detected, wlan0 has been renamed to wlo1.
Apr 24 15:30:07 t111nemesis systemd-networkd[330]: wlo1: Could not bring up interface: Operation not possible due to RF-kill
Apr 24 15:30:10 t111nemesis systemd-networkd[330]: enp0s25: Gained carrier
Apr 24 15:30:11 t111nemesis systemd-networkd[330]: enp0s25: Lost carrier
Apr 24 15:30:11 t111nemesis systemd-networkd[330]: enp0s25: Gained IPv6LL
Apr 24 15:30:13 t111nemesis systemd-networkd[330]: enp0s25: Gained carrier
Apr 24 15:30:15 t111nemesis systemd-networkd[330]: enp0s25: DHCPv4 address 192.168.1.3/24 via 192.168.1.254
Apr 24 15:30:16 t111nemesis systemd-networkd[330]: enp0s25: Configured

Offline

#5 2019-04-24 15:03:38

seth
Member
Registered: 2012-09-03
Posts: 61,191

Re: [SOLVED] Networking messed up: cannot ping domain names

You *must* use exactly one manager (at least per interface) ie choose between NM and systemd-networkd

To be sure:

systemctl list-unit-files --state=enabled

If you're using resolved, ensure to symlink the relevant resolv.conf files, see https://wiki.archlinux.org/index.php/Systemd-resolved

@Lone_Wolf, NM meanwhile seems to default to resolved as well

How to upload text · How to boot w/o GUI · Disable Windows Fast-Start! · Fix your xinitrc

Offline

#6 2019-04-24 15:04:07

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 24,014

Re: [SOLVED] Networking messed up: cannot ping domain names

Network services conflict with each other, decide for one, disable and stop the other (FWIW scouring /etc for whether any configuration is set up doesn't make any statement over which was more "active", NetworkManager will do a lot with default configuration that isn't represented in /etc if you haven't done anything in this regard)

Online

#7 2019-04-24 18:32:37

tlillenuit
Member
From: Ireland
Registered: 2019-03-24
Posts: 28

Re: [SOLVED] Networking messed up: cannot ping domain names

Thanks to everyone! I have managed to solve this issue, by stopping and disabling systemd-networkd service and rebooting. My VPN is working now as well! The only thing that has left, is the booting up is still painfully slow. I would have booted the system up in some 6 seconds since I've got the SSD disk. But this is the theme for another thread.

Offline

Pages: 1

Board footer

Powered by FluxBB