You are not logged in.
I know this is asked often, and I have red many threads, but none could help me.
I'm trying to set up arch on an old Via M811 mainboard. During installation, network was not the slightest problem, but afterwards, after the reboot, I can't get DNS to work.
Ethernet itself is working, ping 8.8.8.8 gives answers, but ping google.com only results in
ping: unknown host google.com
my /etc/resolv.conf:
# Generated by resolvconf
domain Speedport_W_921V_1_34_000
nameserver 192.168.2.1
nameserver fe80::1%eth0
which is the same as on my other arch machines where it is working - apart from the last line.
Of course, I tried deleting the last line, or just a small
nameserver 8.8.8.8
started with dhcpcd -C resolv.conf eth0.
Everything led to the same result.
Has somebody an idea how to get it work?
thanks.
PS:
# dhcpcd
dhcpcd[861]: version 6.3.2 starting
dhcpcd[861]: DUID 00:01:00:......
dhcpcd[861]: eth0: IAID 87:60:78:ce
dhcpcd[861]: eth0: soliciting an IPv6 router
dhcpcd[861]: eth0: rebinding lease of 192.168.2.102
dhcpcd[861]: eth0: Router Advertisement from fe80::1
dhcpcd[861]: eth0: requesting DHCPv6 information
dhcpcd[861]: eth0: leased 192.168.2.102 for 1814400 seconds
dhcpcd[861]: eth0: adding route to 192.168.2.0/24
dhcpcd[861]: eth0: adding default route via 192.168.2.1
dhcpcd[861]: forked to background, child pid 987
maybe "adding route to 192.168.2.0/24" is a problem? the router is 192.168.2.1!
Last edited by Carl Karl (2014-05-08 17:58:10)
Offline
Have you tried disabling IPv6?
I have red many threads
Please, you have to tell us what you have read. It really is helpful in guiding you to a solution.
As to the route, it is not the problem, lest you would not be able to ping 8.8.8.8
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Have you tried disabling IPv6?
Yes, disabling via kernel line worked, but that didn't help with DNS.
Please, you have to tell us what you have read. It really is helpful in guiding you to a solution.
OK, I will post a collection of links to that threads soon.
But before that, there is another interesting thing I found out:
ping localhost doesn't work!
I noticed that the following way:
To be at least able to use pacman, I found out the IP of a mirror, and added it to /etc/hosts:
#
# /etc/hosts: static lookup table for host names
#
#<ip-address> <hostname.domain.org> <hostname>
127.0.0.1 localhost.localdomain localhost
::1 localhost.localdomain localhost
37.58.58.140 leaseweb.net
# End of file
# ping localhost
ping: unknown host localhost
that shouldn't happen IMHO....
Offline
Things I have red and tried:
https://bbs.archlinux.org/viewtopic.php?id=139728 (problem: spelling mistake. don't think I have one...)
https://bbs.archlinux.org/viewtopic.php?id=128409 (outdated solution with rc.conf)
https://wiki.archlinux.org/index.php/resolv.conf
https://wiki.archlinux.org/index.php/Ne … figuration
https://bbs.archlinux.org/viewtopic.php?id=147555 (solved with https://wiki.archlinux.org/index.php/Ne … NS_Servers which didn't help me)
https://bbs.archlinux.org/viewtopic.php?id=167387 (solved by changing router)
https://bbs.archlinux.org/viewtopic.php?id=146404 (was in fact a wifi problem)
Offline
Aaargh! Through the live-system, I pacstraped the host package just to find out:
My DNS IS working!
Just ping isn't working. Strange...
Offline
Carl Karl,
to clarify :
when using something like traceroute google.com the host is found, but with ping it isn't ?
If so, a possible explanation might be that a firewall rule blocks ping somewhere.
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
Thanks, Lone_Wolf. Yes, it was like that. (But without any firewall.)
But meanwhile, the problem vanished: As I had another issue with that installation (mariadb wasn't starting) I discarded that installation and started a new one. This time not from boot USB but from a running arch system and on another hard disk. And with that new installation, everything works. :-)
Last edited by Carl Karl (2014-05-08 17:56:42)
Offline
nameserver fe80::1%eth0
This "IPv6'ey" looking line reminds me of a very similar problem I once had: after my cable provider updated the firmware on my cable modem, my wireless router behind that went on the fritz (no pun intended), and so did my PC running Arch. For some reason things started to fallback or switch to IPv6 here, there and everywhere. The only way I could resolve this was to reboot all of [cable modem, router, PC], after which everything worked as it should.
Note: no, my ISP still doesn't actually support IPv6 (grrr...)
Last edited by ackalker (2014-05-12 19:54:43)
Offline