[SOLVED] Limited Connectivity, can't connect to home network

MarkGotLasagna · 2022-02-24 11:20:36

Hi my name's Mark and I'm currently struggling to connect to my home network.

Before digging into it, I'd like to lay some info that might be useful to diagnose the problem:
my home network (ADSL) is served via a modem (TP-LINK) to which a Pi4 is connected with ether, serving as DNS server with PiHole enabled ("black hole for ads").
To extend the coverage, 2 additional Wi-Fi repeaters are being used (TP-LINK), they inherit the PiHole's DNS server and I'm trying to connect to one of them.

My system, # uname -a

Linux markarch 5.16.10-arch1-1 #1 SMP PREEMPT Wed, 16 Feb 2022 19:35:18 +0000 x86_64 GNU/Linux

running on LENOVO IdeaPad S340 laptop,
using KDE as desktop environment,
has

NetworkManager

enabled, running healthy with no fails whatsoever.

- The problem -
When trying to connect to the home network (SSID: "Wi_Fi"),
the notification center pops a notification saying that the system is "Connected to the network but Internet is unreachable", Limited Connectivity.
After a few moments, the connection is cut altogether.

I've tried connecting to another network (mobile hotspot) and it does that almost instantly.
I've also tried connecting to the same home network using W11 on the same machine (dual boot) and it does indeed connect.
The problem presented itself intermittently a month ago or so (January 2022).

All the other devices on my LAN connect with no failure.

Can I please have your help?

Last edited by MarkGotLasagna (2022-02-24 20:05:02)

Zod · 2022-02-24 12:58:35

Using code tags...
https://bbs.archlinux.org/help.php

please provide the output of

systemctl --type=service --state=running
ip a
ip r
ip link
ping 8.8.8.8
ping archlinux.org

Last edited by Zod (2022-02-24 13:04:36)

MarkGotLasagna · 2022-02-24 13:43:07

Using mobile network 4G LTE:

systemctl --type=service --state=running

  UNIT                      LOAD   ACTIVE SUB     DESCRIPTION                                   
  cups.service              loaded active running CUPS Scheduler
  dbus.service              loaded active running D-Bus System Message Bus
  NetworkManager.service    loaded active running Network Manager
  polkit.service            loaded active running Authorization Manager
  rtkit-daemon.service      loaded active running RealtimeKit Scheduling Policy Service
  sddm.service              loaded active running Simple Desktop Display Manager
  snapd.service             loaded active running Snap Daemon
  sshd.service              loaded active running OpenSSH Daemon
  systemd-journald.service  loaded active running Journal Service
  systemd-logind.service    loaded active running User Login Management
  systemd-resolved.service  loaded active running Network Name Resolution
  systemd-timesyncd.service loaded active running Network Time Synchronization
  systemd-udevd.service     loaded active running Rule-based Manager for Device Events and Files
  udisks2.service           loaded active running Disk Manager
  upower.service            loaded active running Daemon for power management
  user@1000.service         loaded active running User Manager for UID 1000
  wpa_supplicant.service    loaded active running WPA supplicant

LOAD   = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB    = The low-level unit activation state, values depend on unit type.
17 loaded units listed.

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: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether e8:d0:fc:e4:1f:91 brd ff:ff:ff:ff:ff:ff
    inet 192.168.252.72/24 brd 192.168.252.255 scope global dynamic noprefixroute wlp2s0
       valid_lft 3369sec preferred_lft 3369sec
    inet6 fe80::f78e:b0ba:db08:e5cb/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever

ip r

default via 192.168.252.123 dev wlp2s0 proto dhcp metric 600 
192.168.252.0/24 dev wlp2s0 proto kernel scope link src 192.168.252.72 metric 600

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: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether e8:d0:fc:e4:1f:91 brd ff:ff:ff:ff:ff:ff

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=112 time=239 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=112 time=150 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=112 time=194 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=112 time=93.2 ms
^C
--- 8.8.8.8 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 93.155/169.187/239.264/54.089 ms

ping archlinux.org

PING archlinux.org (95.217.163.246) 56(84) bytes of data.
64 bytes from archlinux.org (95.217.163.246): icmp_seq=1 ttl=46 time=98.6 ms
64 bytes from archlinux.org (95.217.163.246): icmp_seq=2 ttl=46 time=236 ms
64 bytes from archlinux.org (95.217.163.246): icmp_seq=3 ttl=46 time=246 ms
64 bytes from archlinux.org (95.217.163.246): icmp_seq=4 ttl=46 time=166 ms
^C
--- archlinux.org ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 98.590/186.721/245.992/59.528 ms

Zod · 2022-02-24 13:50:22

Ok...well good, it's working like a charm.

Don't forget to edit your original post title and mark it solved.

-thc · 2022-02-24 14:23:50

Zod wrote:

Ok...well good, it's working like a charm.

Yes Zod, but did you read the first line of Marks response:

MarkGotLasagna wrote:

Using mobile network 4G LTE:

@MarkGotLasagna: Please reboot your arch box, try to connect to the WiFi and post the output of

sudo journalctl --boot

here.

seth · 2022-02-24 14:24:12

Using mobile network 4G LTE:

That's likely useless because

the notification center pops a notification saying that the system is "Connected to the network but Internet is unreachable", Limited Connectivity.
After a few moments, the connection is cut altogether.

the output in #3 is then pürobably not reflective of this condition.

Do it again when it does *NOT* work and also please post the output of

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

(regardless of when)
In doubt also a complete system journal ("sudo journalctl -b | curl -F 'f:1=<-' ix.io")

Edit: ninja'd…

Last edited by seth (2022-02-24 14:24:41)

MarkGotLasagna · 2022-02-24 14:45:32

-thc wrote:

@MarkGotLasagna: Please reboot your arch box, try to connect to the WiFi and post the output of
sudo journalctl --boot
here.

I created a pastebin with the results of "sudo journalctl --boot", because there are lots of lines.

seth wrote:

Do it again when it does *NOT* work and also please post the output of
find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Here is the output of the command after a failed connection attempt:

cups.socket                              | sockets.target.wants
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service    | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
gcr-ssh-agent.socket                     | sockets.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
iptables.service                         | multi-user.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire-session-manager.service         | user
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
remote-fs.target                         | multi-user.target.wants
snap.certbot.renew.timer                 | timers.target.wants
snapd.socket                             | sockets.target.wants
sshd.service                             | multi-user.target.wants
systemd-resolved.service                 | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
var-lib-snapd-snap-certbot-1670.mount    | multi-user.target.wants
var-lib-snapd-snap-certbot-1788.mount    | multi-user.target.wants
var-lib-snapd-snap-core-12603.mount      | multi-user.target.wants
var-lib-snapd-snap-core-12725.mount      | multi-user.target.wants
var-lib-snapd-snap-core20-1328.mount     | multi-user.target.wants
var-lib-snapd-snap-core20-1361.mount     | multi-user.target.wants
var-lib-snapd-snap-hello\x2dworld-29.mount | multi-user.target.wants
xdg-user-dirs-update.service             | default.target.wants

Here is the URL of the command "sudo journalctl -b | curl -F 'f:1=<-' ix.io":
http://ix.io/3QCy

seth · 2022-02-24 15:13:52

feb 24 15:39:27 markarch NetworkManager[541]: <info>  [1645713567.4712] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
…
feb 24 15:40:12 markarch NetworkManager[541]: <warn>  [1645713612.9678] dhcp4 (wlp2s0): request timed out

You successfully connect to the SSID "MarkS10"
For the SSID "Wi-Fi" you connect, but then don't get a dhcp lease - either because there's a stale lease (parallel windows?) or the router has other issues (reboot the router) or there's a problem w/ the NM dhcp implementation.
For the latter, try to use dhclient, https://wiki.archlinux.org/title/Networ … HCP_client

-thc · 2022-02-24 15:40:28

I assume "MarkS10" is the 4G/WiFi access point (possibly Marks Galaxy S10?) and DHCPv4 is successful:

feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0216] dhcp4 (wlp2s0): state changed unknown -> bound, address=192.168.252.72
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0228] device (wlp2s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
feb 24 15:25:27 markarch dbus-daemon[537]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.3' (uid=0 pid=541 comm="/usr/bin/NetworkManager --no-daemon ")
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0240] policy: set 'MarkS10' (wlp2s0) as default for IPv4 routing and DNS
feb 24 15:25:27 markarch systemd-resolved[532]: wlp2s0: Bus client set default route setting: yes
feb 24 15:25:27 markarch systemd-resolved[532]: wlp2s0: Bus client set DNS server list to: 192.168.252.123
feb 24 15:25:27 markarch systemd[1]: Starting Network Manager Script Dispatcher Service...
feb 24 15:25:27 markarch dbus-daemon[537]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
feb 24 15:25:27 markarch systemd[1]: Started Network Manager Script Dispatcher Service.
feb 24 15:25:27 markarch audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=NetworkManager-dispatcher comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0347] device (wlp2s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0349] device (wlp2s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0354] manager: NetworkManager state is now CONNECTED_SITE
feb 24 15:25:27 markarch NetworkManager[541]: <info>  [1645712727.0360] device (wlp2s0): Activation: successful, device activated.

A few seconds later (15:25:32) he tries to connect to "Wi-Fi" and runs into DHCPv4 timeouts.

I strongly suspect the "WiFi repeater" setup as the culprit.

seth · 2022-02-24 15:51:31

I actually quoted the second attempt, not

feb 24 15:25:39 markarch NetworkManager[541]: <info>  [1645712739.5955] dhcp4 (wlp2s0): activation: beginning transaction (timeout in 45 seconds)
…
feb 24 15:26:24 markarch NetworkManager[541]: <warn>  [1645712784.9682] dhcp4 (wlp2s0): request timed out

but we agree on the condition.

However:

I strongly suspect the "WiFi repeater" setup as the culprit.

All the other devices on my LAN connect with no failure.

I've also tried connecting to the same home network using W11 on the same machine (dual boot) and it does indeed connect.

It might be part of the equation but the claim doesn't support a failure between AP and repeater unless windows ignores the repeater and gets directly to the AP.

MarkGotLasagna · 2022-02-24 16:00:17

After rebooting my router, both the repeaters, and deleting all address reservations in within, a connection was established.

Nevertheless, after a few minutes the connection reverted back to being "Limited",
so before marking this post as SOLVED I'd like to wait sometime and check for a false victory.
I'm currently using my home network and it's working fine (connection isn't that great to begin with).

seth wrote:

I assume "MarkS10" is the 4G/WiFi access point (possibly Marks Galaxy S10?)

"Wi-Fi" is my home network, "MarkS10" is my Galaxy S10 hotspot.

Also I'd like to mention that the repeaters have bundled a DHCP server that can be set to 3 possible modes: Off, On and Auto.
It is currently in "Auto" mode, using any other mode breaks address reservation for all devices inside LAN.

-thc · 2022-02-24 16:03:13

seth wrote:

[...] unless windows ignores the repeater and gets directly to the AP.

This is exactly what I suspect. Windows may also be unable to connect via repeater and silently chooses another AP.

seth · 2022-02-24 16:08:08

Nevertheless, after a few minutes the connection reverted back to being "Limited"

Please post an updated journal, wrt #12, deactivate the repeater and try to connect to the AP directly and in any event, see the 3rd link below.

-thc · 2022-02-24 16:21:26

MarkGotLasagna wrote:

Also I'd like to mention that the repeaters have bundled a DHCP server that can be set to 3 possible modes: Off, On and Auto.
It is currently in "Auto" mode, using any other mode breaks address reservation for all devices inside LAN.

And what does that setting exactly do? There should be only one DHCP server in general.

-thc · 2022-02-24 16:24:45

Double post.

Last edited by -thc (2022-02-24 16:25:01)

MarkGotLasagna · 2022-02-24 16:31:35

seth wrote:

Please post an updated journal, wrt #12, deactivate the repeater and try to connect to the AP directly and in any event, see the 3rd link below.

The updated output of "sudo journalctl -b | curl -F 'f:1=<-' ix.io":
http://ix.io/3QDk

Possible APs within the area are just my repeater#1 (it's ~4m away) and my router.
The other repeater#2 is too far away (~10m) to be picked up.

Connecting to the router directly, after unplugging the repeaters, works fine too with optimal signal strength.

Fast-boot is already disabled, it was one of the first things I've done when dual booting.

-thc wrote:

And what does that setting exactly do? There should be only one DHCP server in general.

Setting it to "On" breaks the address reservation as the router does have a DHCP server already enabled and working.
Setting it to "Off" breaks the ability by the router to even detect the repeaters, this is a problem I've tried to diagnose long time ago with no success, as it is rather peculiar behavior.

seth · 2022-02-24 16:39:34

The router isn't supposed to detect the repeaters but maybe as clients.

If you log into the the repeater, what's the content of the "DHCP Client List" page and how is the repeater configured in "Wireless Settings" (notably the universal/wds/proxy setting)?

MarkGotLasagna · 2022-02-24 16:51:19

seth wrote:

The router isn't supposed to detect the repeaters but maybe as clients.
If you log into the the repeater, what's the content of the "DHCP Client List" page and how is the repeater configured in "Wireless Settings" (notably the universal/wds/proxy setting)?

I'll be posting an update ASAP, can't connect to either tplinkmodem.net nor tplinkrepeater.net as the network is over saturated with clients.

-thc · 2022-02-24 17:07:34

To make it crystal clear: Is your Wi-Fi "repeater" ("WiFi range extender") one of these products:
https://www.tp-link.com/us/home-network … -extender/?

MarkGotLasagna · 2022-02-24 17:19:44

Yes they are, precisely the TL-WA850RE model.

MarkGotLasagna · 2022-02-24 17:40:27

The configuration inside the repeater is in the picture here.

The repeater uses the same SSID as the router.

I repeat that IT IS working as of now. No errors or timeouts.

Last edited by MarkGotLasagna (2022-02-24 17:42:48)

-thc · 2022-02-24 18:27:40

I downloaded the user manual and this DHCP setting is not even mentioned once.

So I hope this setting means something like "If I detect a DHCP server through my wireless settings then I'm off"...

Last edited by -thc (2022-02-24 19:19:56)

MarkGotLasagna · 2022-02-24 20:04:42

I'm marking the post as SOLVED as the connection is stable and no errors showed up in the last hours.

As it turns out, the problem was with the repeater, which was configured in the wrong way.
If you happen to be using a TP-LINK device, make sure no DHCP server is enabled unless you've got one already up and running in your LAN.
Check address reservations too.

Thank you for the help

Arch Linux

#1 2022-02-24 11:20:36

[SOLVED] Limited Connectivity, can't connect to home network

#2 2022-02-24 12:58:35

Re: [SOLVED] Limited Connectivity, can't connect to home network

#3 2022-02-24 13:43:07

Re: [SOLVED] Limited Connectivity, can't connect to home network

#4 2022-02-24 13:50:22

Re: [SOLVED] Limited Connectivity, can't connect to home network

#5 2022-02-24 14:23:50

Re: [SOLVED] Limited Connectivity, can't connect to home network

#6 2022-02-24 14:24:12

Re: [SOLVED] Limited Connectivity, can't connect to home network

#7 2022-02-24 14:45:32

Re: [SOLVED] Limited Connectivity, can't connect to home network

#8 2022-02-24 15:13:52

Re: [SOLVED] Limited Connectivity, can't connect to home network

#9 2022-02-24 15:40:28

Re: [SOLVED] Limited Connectivity, can't connect to home network

#10 2022-02-24 15:51:31

Re: [SOLVED] Limited Connectivity, can't connect to home network

#11 2022-02-24 16:00:17

Re: [SOLVED] Limited Connectivity, can't connect to home network

#12 2022-02-24 16:03:13

Re: [SOLVED] Limited Connectivity, can't connect to home network

#13 2022-02-24 16:08:08

Re: [SOLVED] Limited Connectivity, can't connect to home network

#14 2022-02-24 16:21:26

Re: [SOLVED] Limited Connectivity, can't connect to home network

#15 2022-02-24 16:24:45

Re: [SOLVED] Limited Connectivity, can't connect to home network

#16 2022-02-24 16:31:35

Re: [SOLVED] Limited Connectivity, can't connect to home network

#17 2022-02-24 16:39:34

Re: [SOLVED] Limited Connectivity, can't connect to home network

#18 2022-02-24 16:51:19

Re: [SOLVED] Limited Connectivity, can't connect to home network

#19 2022-02-24 17:07:34

Re: [SOLVED] Limited Connectivity, can't connect to home network

#20 2022-02-24 17:19:44

Re: [SOLVED] Limited Connectivity, can't connect to home network

#21 2022-02-24 17:40:27

Re: [SOLVED] Limited Connectivity, can't connect to home network

#22 2022-02-24 18:27:40

Re: [SOLVED] Limited Connectivity, can't connect to home network

#23 2022-02-24 20:04:42

Re: [SOLVED] Limited Connectivity, can't connect to home network

Board footer