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.
ubuntu 10.10 with broadcom wireless adapter
when i make ping on google i got: time=2000 ms
i tested on another computer i got 350 what the problem?
How, exactly, do you expect anyone here to know that?? There are so many variables involved in a network setup, not to mention you don't say anything about the other computer, the location, etc., that we can't even begin to guess.
There are a lot of a different things that can cause network latency. The first step would be to try and determine if it is a problem with that particular machine, which it sounds like you have been trying to do. When you say you tested with another computer, was everything else the same? For example, was it connected to the same wireless access point with comparable signal strength on the same channel, etc? If it turns out to be related to the computer, you could have a setting mismatch, for example duplex being set to auto on one end and forced to 100 on the other. Another possibility is a routing issue, where sometimes packets can get caught in a routing loop before finally going towards their destination. This is more prone to happen in more complex business networks than simple home LANs.
One tool that might help to determine exactly where the latency is coming from would be pathping (Windows) or Traceroute (Linux). It will show you the route between hosts, such as your PC and google, as well as tell you the time to each step. This will show you if your traffic is getting lost and where the major latency is occurring.
One other thing that just occurred to me is that especially on the first lookup, you could be facing a high DNS resolution time. Try pinging via IP address instead of name to eliminate this possibility.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.