Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
02-04-2005, 01:21 PM
|
#1
|
Member
Registered: Feb 2003
Posts: 149
Rep:
|
Troubleshooting my network
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24102028 errors:1758 dropped:4941 overruns:603 frame:0
TX packets:37347580 errors:0 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:1000
RX bytes:167243708 (159.4 MiB) TX bytes:1901404719 (1.7 GiB)
Interrupt:10 Base address:0xdc00
What are these drops and errors and overruns?
I would like to know when they happend and what caused them
How do I do that?
|
|
|
02-05-2005, 03:32 AM
|
#2
|
Member
Registered: Oct 2004
Location: Australia, Brisbane
Distribution: Gentoo
Posts: 296
Rep:
|
check out the log files in /var/log/
it may help
Regards
|
|
|
02-05-2005, 09:41 AM
|
#3
|
Senior Member
Registered: Dec 2000
Location: Gothenburg, SWEDEN
Distribution: OpenSUSE 10.3
Posts: 1,028
Rep:
|
The errors can be malformed packets or packets broken due to poor cabling, among other things.
|
|
|
02-05-2005, 10:00 AM
|
#4
|
Senior Member
Registered: Jan 2003
Location: Portland, OR USA
Distribution: Slackware, SLAX, Gentoo, RH/Fedora
Posts: 1,024
Rep:
|
If you are connected to the network via a hub this can be the result of packet collisions, which are normal on an unswitched ethernet network, although they normally show up under the collision stat. If you are on wireless, common radio frequency interference (other WAPs, 2.4g phones, many other sources) will cause errors and are also normal.
Like ugge suggested, poor cabling is also a possible candidate, as are cables too short (less than 1 meter) or too long. Cables run near EMI sources such as draped over the flourescent light ballast or behind the microwave oven, or even less drastic interference sources could be a problem.
It's also possible that it's something in your network card. Possibilities include driver issues, IRQ conflicts, or too fast of a network card for a slow system or overloaded PCI bus (gig card in a 486 as an extreme example.)
|
|
|
02-06-2005, 06:05 AM
|
#5
|
Member
Registered: Feb 2003
Posts: 149
Original Poster
Rep:
|
wow ....
Well it got switches and the card is connected to a switch
Poor cables hmm , its neither to long or to sshort .. its like 6meters
Well IŽll check out the log
|
|
|
02-07-2005, 12:22 PM
|
#6
|
Member
Registered: Feb 2003
Posts: 149
Original Poster
Rep:
|
Btw (hope its not to off-topic)
You said it could be bad cable
Well, How do I know they are not bad ? Anyway I can check?
Cuz I dont wanna go and buy a new one if these ones are working alright?
some kinda tool or software?
|
|
|
02-07-2005, 01:54 PM
|
#7
|
Senior Member
Registered: Dec 2000
Location: Gothenburg, SWEDEN
Distribution: OpenSUSE 10.3
Posts: 1,028
Rep:
|
Cabling are tested with expensive testing equipment, so that wouldn't be a choice. (Yes, there are cheap ones, but they wouldn't help in this situation. They only tell if there are connection, not the quality of it)
First rule out all of the other options, then borrow a cable from a frind, then if it solves the problem buy a new one.
|
|
|
All times are GMT -5. The time now is 06:42 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|