You are not logged in.
Pages: 1
the situation: everything works, i'm connected with an ethernet cable, wifi disabled. internet works at 1gigabit speeds as it should
But when i try to ping google.com, or archlinux.org, i get timeouts, 100% loss
pinging 8.8.8.8 works fine, everything cool.
posed no problem until i did need a wget command and it took like ten minutes to process, should have been an instant operation. it worked but took waaaay too long
everything else seems fine, but anytime an url needs to be resolved in terminal, it seems to hang up on something
no issues in surfing or using pacman
am i missing something obvious? is this an issue in my router maybe?
Last edited by drMelski (2025-06-04 02:20:08)
Offline
What's your /etc/resolv.conf look like? Are you using systemd-resolved?
Online
GNU nano 8.4 /etc/resolv.conf
# Generated by NetworkManager
search home telenet.be
nameserver 8.8.8.8
nameserver 195.130.130.3
nameserver 195.130.131.3
# NOTE: the libc resolver may not support more than 3 nameservers.
# The nameservers listed below may not be recognized.
nameserver 2a02:1800:100::43:2
nameserver 2a02:1800:100::43:1
(all this is consistent with my isp settings, and were obtained automatically by networkmgr)
Last edited by drMelski (2025-06-04 04:45:39)
Offline
noob question, how fix?
Offline
tried
ln -sf ../run/systemd/resolve/stub-resolv.conf /etc/resolv.conf
GNU nano 8.4 /etc/resolv.conf
# This is /run/systemd/resolve/stub-resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients to the
# internal DNS stub resolver of systemd-resolved. This file lists all
# configured search domains.
#
# Run "resolvectl status" to see details about the uplink DNS servers
# currently in use.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.
nameserver 127.0.0.53
options edns0 trust-ad
search home telenet.be
Situation the same, tried adding other known dns servers, to no avail
Last edited by drMelski (2025-06-04 03:24:52)
Offline
just checked and it's the same on my archlinux iso when i boot from usb, i can ping 8.8.8.8 but not archlinux.org
same pc on windows (dual boot) has no problems, so cant be the router.
laptop with similar arch install has same problem, so i think it has to do with my config in arch?
had ubuntu before arch and iirc it worked fine there too
ETA: pinging a known ipv4 domain (stoofke.be) works fine, seems pinging domains on ipv6 is the problem. adding ipv6 name server did not help however
Last edited by drMelski (2025-06-04 03:11:08)
Offline
Please use [code][/code] tags. Edit your posts in this regard.
Also please don't bump the thread, edit your previous post to mend it if nobody has yet replied.
Then post the outputs of
ping -c1 google.com
ip a # for the inet6 leases, obfuscate all but the first two fields
In doubt and assuming you've just some bogus IPv6 stack, see https://wiki.archlinux.org/title/IPv6#Disable_IPv6
Online
sorry for the messy post above
wanted to update, the problem has resolved itself on both my machines, without any intervention on my part
no idea if it was an isp issue, a kernel issue, or something else...
i can ping any domain now, and everything works as it should
still puzzled what it was
Offline
Pages: 1