[SOLVED: Router Issue] Can't connect to certain sites

Mileto · 2026-03-19 20:39:42

Recently I noticed i couldn't connect to my wifi using wlan0 in iwd, and read somewhere that I should use NetworkManager instead. It connected normally. Except today, I realized that i couldn't enter most sites, like reddit and github, though google, this forum and the wiki worked just fine.

using ping, I got:

ping: connect: A rede está fora de alcance

(Network is out of reach/Unreachable).

pacman for some reason works??? I thought maybe it was firefox, but after the ping test It got me confused about it. Can someone help me?

Before I forget: I normally use hyprland, but I also have plasma installed, which I'm on currently.

Last edited by Mileto (2026-03-20 21:31:57)

seth · 2026-03-19 20:52:21

ip a; ip r

but you're most likely to some IPv6 https://en.wikipedia.org/wiki/Unique_local_address what would suggest the carrier works but you don't get a lease

using wlan0 in iwd, and read somewhere that I should use NetworkManager instead

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

Did you https://wiki.archlinux.org/title/Iwd#En … figuration ?
Don't.
Also make sure to NOT enable the iwd.service if you're using NM, even if you intend to use iwd as NM backend.

Mileto · 2026-03-19 21:02:14

Here is the output you asked:

dbus-org.freedesktop.network1.service | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.resolve1.service | system
dbus-org.freedesktop.timesync1.service | system
display-manager.service | system
getty@tty1.service | getty.target.wants
iwd.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
pulseaudio.socket | sockets.target.wants
remote-fs.target | multi-user.target.wants
systemd-networkd.service | multi-user.target.wants
systemd-networkd.socket | sockets.target.wants
systemd-networkd-wait-online.service | network-online.target.wants
systemd-network-generator.service | sysinit.target.wants
systemd-resolved.service | sysinit.target.wants
systemd-timesyncd.service | sysinit.target.wants
systemd-userdbd.socket | sockets.target.wants
xdg-user-dirs-update.service | default.target.wants

I completely forgot to mention, but i also tried changing DHCP settings on NetworkManager, since I'm using it now instead of iwd.

And no, i haven't messed with that part.

Last edited by Mileto (2026-03-19 21:23:46)

seth · 2026-03-19 21:07:18

seth wrote:

ip a; ip r

However: disable iwd.service and everything systemd-networkd*, reboot, check the behavior, if it's not working please post your complete system journal for the boot:

sudo journalctl -b | curl -F 'file=@-' https://0x0.st

Last edited by seth (2026-03-19 21:07:30)

Mileto · 2026-03-19 21:26:11

Here is the output i forgot about:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu ----- qdisc noqueue state UNKNOWN group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host noprefixroute
valid_lft forever preferred_lft forever
2: ens1f1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
link/ether brd ff:ff:ff:ff:ff:ff
altname
altname
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
link/ether brd ff:ff:ff:ff:ff:ff
inet6 scope global dynamic noprefixroute
valid_lft 2144447866sec preferred_lft 2144447866sec
inet6 scope global dynamic mngtmpaddr noprefixroute
valid_lft 2144447866sec preferred_lft 2144447866sec
inet6 scope link noprefixroute
valid_lft forever preferred_lft forever

About the journal, is the link enough, or should i post it here as a quote?

Last edited by Mileto (2026-03-19 22:50:06)

Mileto · 2026-03-19 21:29:02

Oh, and the behavior, of course. When i rebooted the system, wifi refused to even connect, and no networks were found. As soon as i turned it on again, it started working again.

Here's the journal link: -

Edited out in favour of the new link

Last edited by Mileto (2026-03-19 21:46:26)

seth · 2026-03-19 21:32:05

Link will do, you don't have an IPv4 lease (is this after fixing the services and rebooting?)
But edit the post and obfuscate the lines that start w/ "inet6 2804:214", they're globally routable IPv6 in the Bay of All the Saints

Edit: iwd, networkd and NetworkManager are all enabled in that journal

Last edited by seth (2026-03-19 21:33:42)

Mileto · 2026-03-19 21:37:48

Sorry, i'm a huge newbie on all this... So, i didn't report the journal from before i had to turn iwd on again, since i couldn't connect to wifi (and i don't have any ethernet cables as of now). I'll get on with it and save the journal in a .txt.

About network d, output when trying to remove it is as follows:

systemctl disable systemmd-networkd*
Glob pattern passed to disable, but globs are not supported for this.
Invalid unit name "systemmd-networkd*" escaped as "systemmd-networkd\x2a".
Failed to disable unit: Unit systemmd-networkd\x2a.service does not exist

Mileto · 2026-03-19 21:43:29

For some reason, this time wifi started working on itself after the reboot. Still can't access github and reddit though. Here's the new journal:

Ton of adress in this link, i'm editing it out

Last edited by Mileto (2026-03-19 22:19:49)

seth · 2026-03-19 21:55:12

networkd is still enabled

systemctl disable --now systemd-networkd.socket
systemctl disable --now systemd-networkd.service
systemctl disable --now systemd-networkd-wait-online.service
systemctl restart NetworkManager.service

There's no dhcp v4 response, might be just because of the collision but what is "LIVE TIM_692A_2G" some routerswitchmodem device you got from your ISP?

Mileto · 2026-03-19 22:01:28

I disabled them and restarted NM, but i still can't access sites. Should i reboot and test again?

LIVE TIM Is the network name, i just left the default one. And yes, it's a modem, not sure what routerswitchmodem is, but i can check if that's important.

By the way, should i be worried about the ip6 thing i posted? I didn't know that could be dangerous, kinda misinformed.

Edit: Yes, it's exactly that, it provides internet, has ethernet slots and wifi connectivity. Also, are there any steps i could take to ensure better safety now that i potentially doxxed myself?

Last edited by Mileto (2026-03-19 22:04:28)

seth · 2026-03-19 22:06:48

not sure what routerswitchmodem is

The boxes colloquially called "router" or "modem" are integrated devices that actually do a lot of things.
Speaking of which, let's see whether there's a dhcp server

sudo nmap --script broadcast-dhcp-discover

I didn't know that could be dangerous, kinda misinformed.

Not "dangerous" but identifying, it's mostly a privacy concern.

Mileto · 2026-03-19 22:11:36

sudo nmap --script broadcast-dhcp-discover
sudo: nmap: comando não encontrado

nmap: command wasn't found.

seth · 2026-03-19 22:16:57

https://archlinux.org/packages/extra/x86_64/nmap/
Since you apparently tried

mar 19 18:39:29 miletooo NetworkManager[443]: <warn>  [1773956369.2232] dhcp: init: DHCP client 'dhclient' not available

https://archlinux.org/packages/extra/x86_64/dhclient/
Might be a good idea if there's a dhcp server but it doesn't want to talk to the NM internal implementation.

Mileto · 2026-03-19 22:25:18

I really don't mean to offend, as i said before i'm very dumb when it comes to it stuff, but is the nmap scan necessary? first google result was about how it's not a good idea to share those, and i kinda already doxxed myself before...

Last edited by Mileto (2026-03-19 22:26:20)

Mileto · 2026-03-19 22:47:27

I tried and failed to install nmap, so i'll be giving up on solving this for now. It was a previous problem that i was already delaying to solve, so i probably either need to fix that first, or just do a fresh install of arch if i can't solve.

nmap-7.98-5-x86_64 5,9 MiB 589 KiB/s 00:10 [##############################################] 100%
(3/3) verificando chaves no chaveiro [##############################################] 100%
(3/3) verificando integridade do pacote [##############################################] 100%
(3/3) carregando arquivos do pacote [##############################################] 100%
(3/3) verificando conflitos de arquivos [##############################################] 100%
erro: falha ao efetuar a transação (arquivos conflitantes)
libgcc: /usr/lib/libgcc_s.so existe no sistema de arquivos (pertence a gcc-libs)
libgcc: /usr/lib/libgcc_s.so.1 existe no sistema de arquivos (pertence a gcc-libs)
libgcc: /usr/share/licenses/gcc-libs/RUNTIME.LIBRARY.EXCEPTION existe no sistema de arquivos (pertence a gcc-libs)
libstdc++: /usr/lib/libstdc++.so existe no sistema de arquivos (pertence a gcc-libs)
libstdc++: /usr/lib/libstdc++.so.6 existe no sistema de arquivos (pertence a gcc-libs)
libstdc++: /usr/share/locale/de/LC_MESSAGES/libstdc++.mo existe no sistema de arquivos (pertence a gcc-libs)
libstdc++: /usr/share/locale/fr/LC_MESSAGES/libstdc++.mo existe no sistema de arquivos (pertence a gcc-libs)
Ocorreram erros e, portanto, nenhum pacote foi atualizado.

Edit: Also, i downloaded dhclient, and created the dhcp config file as by the wiki, but it didn't change anything. I'll try to reboot it one last time to see if it's that.

Last edited by Mileto (2026-03-19 22:48:41)

loqs · 2026-03-19 23:01:46

The update appears to have failed as it was a partial upgrade that did not include the changes related to the splitting of gcc-libs.

seth · 2026-03-20 07:54:56

Fwwi the nmap call will not doxx anything, only tell whether and how many dhcp servers are in the network.
Don't run partial updates, dhclient might have been installed before but unable to resolve linked libraries.

Mileto · 2026-03-20 21:31:32

UPDATE: I decided to fresh install arch, so i tried accessing the download page from my dad's PC. Guess what. Same issue. My personal PC? Same thing. I tried messing with some router configs in hope it would change something, and even formated it, to no avail. In the end, all my devices are like that, and that made me realize that this is a router issue. I'm entering in contact with my ISP to solve this,

TL;DR: It was a router issue in the end.

seth · 2026-03-20 21:44:53

Your ISP might not provide IPv4, https://de.wikipedia.org/wiki/Liste_von … nelbrokern (you'll need 4in6)

Arch Linux

#1 2026-03-19 20:39:42

[SOLVED: Router Issue] Can't connect to certain sites

#2 2026-03-19 20:52:21

Re: [SOLVED: Router Issue] Can't connect to certain sites

#3 2026-03-19 21:02:14

Re: [SOLVED: Router Issue] Can't connect to certain sites

#4 2026-03-19 21:07:18

Re: [SOLVED: Router Issue] Can't connect to certain sites

#5 2026-03-19 21:26:11

Re: [SOLVED: Router Issue] Can't connect to certain sites

#6 2026-03-19 21:29:02

Re: [SOLVED: Router Issue] Can't connect to certain sites

#7 2026-03-19 21:32:05

Re: [SOLVED: Router Issue] Can't connect to certain sites

#8 2026-03-19 21:37:48

Re: [SOLVED: Router Issue] Can't connect to certain sites

#9 2026-03-19 21:43:29

Re: [SOLVED: Router Issue] Can't connect to certain sites

#10 2026-03-19 21:55:12

Re: [SOLVED: Router Issue] Can't connect to certain sites

#11 2026-03-19 22:01:28

Re: [SOLVED: Router Issue] Can't connect to certain sites

#12 2026-03-19 22:06:48

Re: [SOLVED: Router Issue] Can't connect to certain sites

#13 2026-03-19 22:11:36

Re: [SOLVED: Router Issue] Can't connect to certain sites

#14 2026-03-19 22:16:57

Re: [SOLVED: Router Issue] Can't connect to certain sites

#15 2026-03-19 22:25:18

Re: [SOLVED: Router Issue] Can't connect to certain sites

#16 2026-03-19 22:47:27

Re: [SOLVED: Router Issue] Can't connect to certain sites

#17 2026-03-19 23:01:46

Re: [SOLVED: Router Issue] Can't connect to certain sites

#18 2026-03-20 07:54:56

Re: [SOLVED: Router Issue] Can't connect to certain sites

#19 2026-03-20 21:31:32

Re: [SOLVED: Router Issue] Can't connect to certain sites

#20 2026-03-20 21:44:53

Re: [SOLVED: Router Issue] Can't connect to certain sites

Board footer