Again, thank you all for sparing some time to help me out. I really appreciate it.
fungal_net wroteYou seem to have an ip address, I suspect your router's ip is 192.168.122.1 and your's is " " " 63 the only thing unusual from your ip output is your preferred/valid lft (lifetime) that is limited, but it is configured to last an hour.
You mean my host address, right? Well, my IP is totally different than that (wlan0: 192.168.0.106/24), but it is indeed 192.168.122.1/24 in virbr0 (I don't even know what that is). Does that make sense?
fungal_net wroteTry this command: sudo ping -c 2 wiki.archlinux.org see if the ping command resolves the name archli..org into an IP number. Also try sudo ping -c 2 wiki.obarun.org
Is it possible your router only has ipv6 DNS or 4 only and blocks the other?
So also try sudo ping -c 3 news.google.com
See if it resolves to an ipv4 or 6 address or nothing at all.
All of them resulted in the same error.
ping: <domain>: System error
fungal_net wroteIf both ping attempts don't resolve an ip number then it is a dns error. I assume: sudo ping -c 2 192.168.122.1 gives you a result, even though negative as if the router is denying ping requests.
A positive one, actually. 2 packets transmitted, 2 received.
fungal_net wroteYou can try to edit the boot command on the syslinux screen by hitting Tab
at the end of the line add net.ifnames=0 ipv6.disable=1 alternatively ipv4.disable=1
The one disables ipv6 the other ipv4, then log in and see ip a
If I understood correctly, I should put this as kernel parameters, right? In this case, "tab" didn't work for me, but pressing "e" before entering live CD did.
In both cases, IP address were still in the same range, and pinging the host still worked. One thing that changed is that I didn't need "sudo" anymore (?).
Disabling IPv4 gave the same errors, but disabling IPv6 print the following output:
ping: socket: Address family not supported by protocol
ping: <domain>: System error
jean-michel wroteSo, everythings looks good, can you now check your /etc/resolv.conf file and verify that you have nameserver IP defined or past the output of this file.
Only comments. :O
$ cat /etc/resolv.conf
# Generated by dhcpcd
# /etc/resolv.conf.head can replace this line
# /etc/resolv.conf.tail can replace this line