You are not logged in.

#1 2021-07-02 00:15:12

RVA965
Member
Registered: 2020-12-23
Posts: 3

Network Issue despite having an ip and dns resolution

I am using NetworkManager out of the box with systemd-resolved and /etc/resolv.conf symlinked to /run/systemd/resolve/resolv.conf. I do not have any external programs like dhcpcd running that would conflict.

I can connect to all private networks, but when I try connecting to a public wifi network, NetworkManager will connect me, but I am not able to access the internet.
I am pretty sure DNS resolution happens because there are nameservers in /etc/resolv.conf

nameserver 172.16.17.19
nameserver 172.16.17.20
nameserver 8.8.8.8
search .

Additionally, I can see that things should work because when I execute ping www.google.com, i get

PING www.google.com (172.217.9.196) 56(84) bytes of data.

Here is the output of ip a which shows

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: enp8s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 80:fa:5b:7b:ce:24 brd ff:ff:ff:ff:ff:ff
3: wlp0s20f3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether 0c:7a:15:0c:58:dc brd ff:ff:ff:ff:ff:ff
    inet 10.201.131.71/24 brd 10.201.131.255 scope global dynamic noprefixroute wlp0s20f3
       valid_lft 574sec preferred_lft 574sec
    inet6 fe80::7b14:cfb6:11e0:274d/64 scope link noprefixroute
       valid_lft forever preferred_lft forever

that I have an ip address.

Running resolvectl gives

Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: uplink
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

Link 2 (enp8s0)
Current Scopes: none
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (wlp0s20f3)
    Current Scopes: DNS LLMNR/IPv4 LLMNR/IPv6
         Protocols: +DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported
Current DNS Server: 172.16.17.20
       DNS Servers: 172.16.17.19 172.16.17.20 8.8.8.8

Despite everything pointing to the fact that I should have a working connection, I can neither ping any server (100% packet loss) nor access anything within a browser. I know this is not a hardware issue because I have a windows system on a separate hardware drive that can connect to this network just fine. None of the systemd units have failed. I have tried disabing systemd-resolved and letting NetworkManager edit /etc/resolv.conf itself, and that did not work. I have tried disabling syncing to NTP within timedatectl and that did not work.

Below I have included my journalctl logs that get spit out when I restart NetworkManager.service.

Jul 01 19:32:57 RVA kernel: wlp0s20f3: deauthenticating from 62:42:75:9e:32:ac by local choice (Reason: 3=DEAUTH_LEAVING)
Jul 01 19:32:57 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-DISCONNECTED bssid=62:42:75:9e:32:ac reason=3 locally_generated=1
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8218] device (wlp0s20f3): supplicant interface state: completed -> disconnected
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8218] device (p2p-dev-wlp0s20f3): supplicant management interface state: completed -> disconnected
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8219] device (wlp0s20f3): state change: deactivating -> disconnected (reason 'new-activation', sys-iface-state: 'managed')
Jul 01 19:32:57 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=0 signal=0 noise=9999 txrate=0
Jul 01 19:32:57 RVA systemd-resolved[419]: wlp0s20f3: Bus client set DNS server list to: fe80::1881:51ab:5f96:8e1c
Jul 01 19:32:57 RVA systemd-resolved[419]: wlp0s20f3: Bus client set default route setting: no
Jul 01 19:32:57 RVA systemd-resolved[419]: wlp0s20f3: Bus client reset DNS server list.
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8593] dhcp4 (wlp0s20f3): canceled DHCP transaction
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8593] dhcp4 (wlp0s20f3): state changed bound -> terminated
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8598] dhcp6 (wlp0s20f3): canceled DHCP transaction
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8598] dhcp6 (wlp0s20f3): state changed bound -> terminated
Jul 01 19:32:57 RVA NetworkManager[448]: <info>  [1625182377.8787] device (wlp0s20f3): set-hw-addr: set MAC address to 32:5C:29:61:FF:6A (scanning)
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0876] manager: NetworkManager state is now DISCONNECTED
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0877] device (wlp0s20f3): Activation: starting connection 'MCGUEST-LIBRARY' (12e792f3-a690-46bb-a2fd-7d38d2b2bb2f)
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0882] device (wlp0s20f3): supplicant interface state: disconnected -> interface_disabled
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0882] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> interface_disabled
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0885] device (wlp0s20f3): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.0886] manager: NetworkManager state is now CONNECTING
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.1020] device (wlp0s20f3): set-hw-addr: reset MAC address to 0C:7A:15:0C:58:DC (preserve)
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3126] device (wlp0s20f3): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3131] device (wlp0s20f3): Activation: (wifi) connection 'MCGUEST-LIBRARY' requires no security.  No secrets needed.
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3132] Config: added 'ssid' value 'MCGUEST-LIBRARY'
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3133] Config: added 'scan_ssid' value '1'
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3133] Config: added 'bgscan' value 'simple:30:-70:86400'
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.3133] Config: added 'key_mgmt' value 'NONE'
Jul 01 19:32:58 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=WORLD
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.4015] device (wlp0s20f3): supplicant interface state: interface_disabled -> disconnected
Jul 01 19:32:58 RVA NetworkManager[448]: <info>  [1625182378.4016] device (p2p-dev-wlp0s20f3): supplicant management interface state: interface_disabled -> disconnected
Jul 01 19:32:58 RVA systemd-resolved[419]: Switching to fallback DNS server 1.1.1.1.
Jul 01 19:33:01 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=US
Jul 01 19:33:01 RVA NetworkManager[448]: <info>  [1625182381.4151] device (wlp0s20f3): supplicant interface state: disconnected -> scanning
Jul 01 19:33:01 RVA NetworkManager[448]: <info>  [1625182381.4152] device (p2p-dev-wlp0s20f3): supplicant management interface state: disconnected -> scanning
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: SME: Trying to authenticate with f4:2e:7f:3d:3d:90 (SSID='MCGUEST-LIBRARY' freq=5500 MHz)
Jul 01 19:33:03 RVA kernel: wlp0s20f3: authenticate with f4:2e:7f:3d:3d:90
Jul 01 19:33:03 RVA kernel: wlp0s20f3: send auth to f4:2e:7f:3d:3d:90 (try 1/3)
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.2892] device (wlp0s20f3): supplicant interface state: scanning -> authenticating
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.2892] device (p2p-dev-wlp0s20f3): supplicant management interface state: scanning -> authenticating
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: Trying to associate with f4:2e:7f:3d:3d:90 (SSID='MCGUEST-LIBRARY' freq=5500 MHz)
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3274] device (wlp0s20f3): supplicant interface state: authenticating -> associating
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3275] device (p2p-dev-wlp0s20f3): supplicant management interface state: authenticating -> associating
Jul 01 19:33:03 RVA kernel: wlp0s20f3: authenticated
Jul 01 19:33:03 RVA kernel: wlp0s20f3: associate with f4:2e:7f:3d:3d:90 (try 1/3)
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: Associated with f4:2e:7f:3d:3d:90
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-CONNECTED - Connection to f4:2e:7f:3d:3d:90 completed [id=0 id_str=]
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-SUBNET-STATUS-UPDATE status=0
Jul 01 19:33:03 RVA kernel: wlp0s20f3: RX AssocResp from f4:2e:7f:3d:3d:90 (capab=0x401 status=0 aid=5)
Jul 01 19:33:03 RVA kernel: wlp0s20f3: associated
Jul 01 19:33:03 RVA kernel: IPv6: ADDRCONF(NETDEV_CHANGE): wlp0s20f3: link becomes ready
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3403] device (wlp0s20f3): supplicant interface state: associating -> completed
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3404] device (wlp0s20f3): Activation: (wifi) Stage 2 of 5 (Device Configure) successful. Connected to wireless network "MCGUEST-LIBRARY"
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3404] device (p2p-dev-wlp0s20f3): supplicant management interface state: associating -> completed
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3416] device (wlp0s20f3): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3426] dhcp4 (wlp0s20f3): activation: beginning transaction (timeout in 45 seconds)
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3572] dhcp4 (wlp0s20f3): state changed unknown -> bound, address=10.201.131.71
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3581] device (wlp0s20f3): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3590] device (wlp0s20f3): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3592] device (wlp0s20f3): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3594] manager: NetworkManager state is now CONNECTED_LOCAL
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3598] manager: NetworkManager state is now CONNECTED_SITE
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3599] policy: set 'MCGUEST-LIBRARY' (wlp0s20f3) as default for IPv4 routing and DNS
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.3602] device (wlp0s20f3): Activation: successful, device activated.
Jul 01 19:33:03 RVA systemd-resolved[419]: wlp0s20f3: Bus client set default route setting: yes
Jul 01 19:33:03 RVA systemd-resolved[419]: wlp0s20f3: Bus client set DNS server list to: 172.16.17.19, 172.16.17.20, 8.8.8.8
Jul 01 19:33:03 RVA nm-dispatcher[3697]:   % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Jul 01 19:33:03 RVA nm-dispatcher[3697]:                                  Dload  Upload   Total   Spent    Left  Speed
Jul 01 19:33:03 RVA wpa_supplicant[681]: wlp0s20f3: CTRL-EVENT-SIGNAL-CHANGE above=1 signal=-39 noise=9999 txrate=866700
Jul 01 19:33:03 RVA nm-dispatcher[3697]: [158B blob data]
Jul 01 19:33:03 RVA dbus-daemon[447]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.109' (uid=0 pid=3699 comm="timedatectl set-timezone America/New_York ")
Jul 01 19:33:03 RVA audit: BPF prog-id=64 op=LOAD
Jul 01 19:33:03 RVA audit: BPF prog-id=65 op=LOAD
Jul 01 19:33:03 RVA audit: BPF prog-id=66 op=LOAD
Jul 01 19:33:03 RVA systemd[1]: Starting Time & Date Service...
Jul 01 19:33:03 RVA kernel: audit: type=1334 audit(1625182383.684:253): prog-id=64 op=LOAD
Jul 01 19:33:03 RVA kernel: audit: type=1334 audit(1625182383.684:254): prog-id=65 op=LOAD
Jul 01 19:33:03 RVA kernel: audit: type=1334 audit(1625182383.684:255): prog-id=66 op=LOAD
Jul 01 19:33:03 RVA dbus-daemon[447]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jul 01 19:33:03 RVA systemd[1]: Started Time & Date Service.
Jul 01 19:33:03 RVA audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:03 RVA kernel: audit: type=1130 audit(1625182383.704:256): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:03 RVA NetworkManager[448]: <info>  [1625182383.8008] manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 01 19:33:13 RVA systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
Jul 01 19:33:13 RVA audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:13 RVA kernel: audit: type=1131 audit(1625182393.975:257): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:33 RVA systemd[1]: systemd-timedated.service: Deactivated successfully.
Jul 01 19:33:33 RVA audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:33 RVA kernel: audit: type=1131 audit(1625182413.737:258): pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-timedated comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
Jul 01 19:33:33 RVA audit: BPF prog-id=66 op=UNLOAD
Jul 01 19:33:33 RVA audit: BPF prog-id=65 op=UNLOAD
Jul 01 19:33:33 RVA audit: BPF prog-id=64 op=UNLOAD
Jul 01 19:33:33 RVA kernel: audit: type=1334 audit(1625182413.787:259): prog-id=66 op=UNLOAD
Jul 01 19:33:33 RVA kernel: audit: type=1334 audit(1625182413.787:260): prog-id=65 op=UNLOAD
Jul 01 19:33:33 RVA kernel: audit: type=1334 audit(1625182413.787:261): prog-id=64 op=UNLOAD
Jul 01 19:36:50 RVA systemd-timesyncd[2471]: Timed out waiting for reply from 95.216.218.15:123 (0.arch.pool.ntp.org).
Jul 01 19:37:01 RVA systemd-timesyncd[2471]: Timed out waiting for reply from 5.34.248.225:123 (0.arch.pool.ntp.org).
Jul 01 19:37:11 RVA systemd-timesyncd[2471]: Timed out waiting for reply from 198.74.51.125:123 (0.arch.pool.ntp.org).

Offline

#2 2021-07-02 01:04:01

Piri
Member
Registered: 2018-06-02
Posts: 64

Re: Network Issue despite having an ip and dns resolution

You are talking about a public network. Does it have a captive portal? If so, have you properly authenticated against it?

https://wiki.archlinux.org/title/Networ … ve_portals

Offline

#3 2021-07-02 01:35:39

RVA965
Member
Registered: 2020-12-23
Posts: 3

Re: Network Issue despite having an ip and dns resolution

I am quite sure the network did not have a captive portal as I connected both on a windows machine and an iPhone, and they did not bring any portal up and instead just connected me. When I go back, I will make sure though.

Offline

#4 2021-07-02 06:31:56

seth
Member
Registered: 2012-09-03
Posts: 22,180

Re: Network Issue despite having an ip and dns resolution

tracepath google.com

Offline

Board footer

Powered by FluxBB