You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
You need to add the -4 command switch so that it will only try IPv4:
ping -4 google.com
Otherwise, ping will use whatever address the target resolves to, IPv4 or IPv6.
You can create an alias for this in your profile.
I tried doing this, but I still seem to be getting the same error. The screenshots are from vmware, and yes it seems to work when I resolve the nameserver to use google's server within resolv.conf. I'm just now realizing the issue lies in my openbsd, the 192.168.54.71 address, which is now also unable to ping google.com, even though it was able to before.
I feel as though the issue lies in this file, and I have on idea how I'd be able to fix it.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Accept
Learn more…
