Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
when I type this command in ubuntu 14
$ping archive.ubuntu.com
I get this ....
ping archive.ubuntu.com (91.189.88.152) 56(84) bytes of data.
and then it stucks there forever
what do we conclude from this ?
That you can't ping that IP address.
Quote:
Originally Posted by Volcano
Can we say that its connected to internet ( since IP is resolved ) but firewall is blocking the ping ?
There could be an entry in /etc/hosts, or your system could be using an internal resolver on your local network, so the fact that it's "resolving" doesn't mean that the system has internet connectivity.
Quote:
Originally Posted by Volcano
if not what can we conclude with this response ?
We can conclude that you've not provided enough information to aid troubleshooting.
Try traceroute. Confirm you can ping 8.8.8.8 ok (or not).
My troubleshooting concept is to collect more 'data points'
(I/detectives call it clues/evidence), rather than stop at
"fw may be guilty, [simply] because ping found dead".
Ubuntu installs dnsmasq as a DNS cache by default which is why you see the 127.0.1.1 in the hosts file. I would assume that the hostname is ubuntu. This could be the reason for it to resolve the IP address but hang on the output.
Did networking work at one time? If so do you remember if you made any changes or maybe an update caused your problems?
Ubuntu installs dnsmasq as a DNS cache by default which is why you see the 127.0.1.1 in the hosts file. I would assume that the hostname is ubuntu. This could be the reason for it to resolve the IP address but hang on the output.
Did networking work at one time? If so do you remember if you made any changes or maybe an update caused your problems?
Its just freshly installed from ubuntu 14 AMD 64 bit ISO. No changes done
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.