You are not logged in.
So I'm not really sure whats happening here, but I'm not able to ping certain URLs. It seems that my nameserver isn't resolving URLS to the correct IPV6 addresses. For example, if i try to ping Google:
PING google.com(iad23s72-in-x0e.1e100.net (2607:f8b0:4004:80a::200e)) 56 data bytes
and I get 100% packet loss.
However, if I ping forbes, all packets are returned, but its using an IPV4 address. If I ping 2001:4860:4860::8888 (Googles DNS for IPV6) I can't reach it. I don't really know what else to include, but its causing problems because I can't reach some websites.
Offline
Do you have valid IPv6 address and properly set up IPv6 routing?
Gnome - The weakest link!
Linux, *not* GNU/Linux!
Offline
Does your default gateway support IPv6?
Offline
Does your default gateway support IPv6?
Yes
Do you have valid IPv6 address and properly set up IPv6 routing?
I haven't done anything with IPV6. I was under the impression that Arch set everything without me having to do anything. (Then again, I probably shouldn't have thought that lol) How would I go about that? Or is there a way to set it so that everything is resolved to IPV4?
Offline
The problem might be somewhere else then your system, like the network setup of your provider.
(some providers advertise IPv6 support but only provide a 6to4 tunnel, not full ipv6 ).
Let's check if you can reach archlinux,org over both ipv4 and ipv6 .
$ traceroute 138.201.81.199
$ traceroute 2a01:4f8:172:1d86::1
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
What does
ip -6 route
say?
Offline