On 05/11/16 10:40, Reiner Herrmann wrote: > On Sat, Nov 05, 2016 at 10:32:21AM +1300, Aidan Gauland wrote: >>>> $ w3m google.com >>>> w3m: Can't load google.com. >>> >>> The same error occurs when only DNS is not working. >>> Can you please try pinging your default gateway? >> >> Yes, pinging the default gateway works just fine with 0% packet loss >> (tested with 20 packets). > > Interesting, then I assume pinging an external IP address also works > (like 8.8.8.8)? Can you check /etc/resolv.conf if a valid nameserver > is configured?
I can successfully ping 8.8.8.8, and the contents of /etc/resolv.conf both in and out of the sandbox is the single line, nameserver fe80::c6e9:84ff:fe9f:7bb2%eth0 > I saw that you are running rdnssd, which might overwrite > /etc/resolv.conf. I think rdnssd was part of the base Debian installation, so that shouldn't suddenly be causing problems now. Could it?
signature.asc
Description: OpenPGP digital signature
