LinuxQuestions.org
Register a domain and help support LQ
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Hardware
User Name
Password
Linux - Hardware This forum is for Hardware issues.
Having trouble installing a piece of hardware? Want to know if that peripheral is compatible with Linux?

Notices

Reply
 
Search this Thread
Old 03-12-2004, 10:53 AM   #1
Micah
Member
 
Registered: Apr 2002
Location: OK, USA
Distribution: Slackware64 14
Posts: 180

Rep: Reputation: 31
Question What can cause packet loss?


What will cause my network card to start dropping packets?

Info:
Everything worked perfect but I ran out of space and couldn't install the latest gcc. So I rebuilt with a new distro (that already had it). Since rebuilding, my network cards will stop dropping packets when put under any load.

Examples of what causes the network to brake:
Opening a webpage with graphics (google.com)
Downloadign a file with lynx
FTP operations that are large (kernel.org list of kernels for 2.2.x)
Rdesktop
vncserver (once someone connects)

Network cards:
IBM 10/100 EtherJet - 32bit Cardbus Adapter
Encore 10/100 Base-TX ethernet PC Card (uses rtl8139 chipset)

Kernels used: 2.2.17, 2.2.19, 2.2.26
PCMCIA-CS drivers used: 3.2.4, 3.2.7
Distributions used: Slackware 7.1, 8.0, 9.1
Computer: Thinkpad 760XL (Laptop) using PCMCIA interface for NICs

Again, my question is what 'could' be causing my network packets to start dropping?

Thanks for ANY input.
 
Old 03-12-2004, 11:04 AM   #2
dushkinup
Member
 
Registered: Feb 2004
Location: Alpha Quadrant, sol system, earth, asia, Israel.
Distribution: Computer I : Slackware 9.1 ; Computer II : Windows XP
Posts: 144

Rep: Reputation: 15
Poor network conditions.
Things like bad cables, bad network cards in the worse case.

It's hard to believe It's GCC who made you start loosing packets, but maybe. You should try testing your hardware on other computers if you can. And try testing the cables with a special device (I know someone who has one, dunno where he bought it).

Packet loss is a very bad thing (as you can see).
Get rid of it.
 
Old 03-12-2004, 11:36 AM   #3
Micah
Member
 
Registered: Apr 2002
Location: OK, USA
Distribution: Slackware64 14
Posts: 180

Original Poster
Rep: Reputation: 31
Oops... GCC caused me to rebuild my box. Since rebuilding everything has been out of whack. (When I tried to install GCC, I deleted all MAN files, all info files, all files I didn't know what they were for... After I was done, I couldn't open X Windows and GCC still couldn't be built) - So I reinstalled and got these problems.

As far as conditions goes:
I have tested this at work and at home with the same problems. At both locations I use different cables. I will change cables to see if that helps.
 
Old 03-14-2004, 01:38 PM   #4
Micah
Member
 
Registered: Apr 2002
Location: OK, USA
Distribution: Slackware64 14
Posts: 180

Original Poster
Rep: Reputation: 31
Ok, I have now tested my NIC with a Windows XP box and it works perfect! I have tested with other CAT5 cables and it still fails. Network cables test out fine (At work we have all the fun stuff =)

Anything else?
 
Old 03-14-2004, 02:00 PM   #5
thelandrew
Member
 
Registered: Mar 2004
Posts: 30

Rep: Reputation: 16
Um... I'm still a linux newbie, but I don't think your problem is linux per se, so if you had windoze on that system...

Packet loss on small peer to peer networks can be caused by almost anything. Check, in this order:

1) The cables. If possible, replace your cable with a known good cable. Don't test when you can replace.

2) The driver. An incorrect driver which appears to be correct can cause packet loss. Update the driver if possible. Confirm you have the BEST driver.

3) Cable Stress. Similar to (1) If a cable is often bent at a particular (sharp) angle, it may over time stop working EXCEPT when bent in that way.

4) Your NIC. Nics can fail in all kinds of interesting ways. In addition to electronic failure, I have seen NICs that suffer from "cable stress" in their rj45 ports. Replace the NIC if possible.

.

.

.

.

99) Cosmic Radiation. You'd be surprised how much harm a stray alpha particle can do to a data transmission. Seal your entire network behind 3 meters of lead...

100) Alien intervention. Maybe "they" are experimenting on you? Wear a tinfoil hat and your performance should improve.


Based on what you've already said, by bet is that you have a a bad or misconfigured driver for your NIC. How to fix? No Idea. You'll need someone who knows beans about linux.

-landrew the

Last edited by thelandrew; 03-14-2004 at 02:01 PM.
 
1 members found this post helpful.
Old 03-14-2004, 03:24 PM   #6
Micah
Member
 
Registered: Apr 2002
Location: OK, USA
Distribution: Slackware64 14
Posts: 180

Original Poster
Rep: Reputation: 31
Lead is expensive and I don't have any tinfoil -- Thank good ness...

More Info:
My restoration of my backup completed and it works... I do get droppedpackets, BUT it recovers and continues!

What Config files do I need to look at? (A bit off topic)

PS:
NIC works perfect in other PCs (Windows anyhow)
The latest driver failed too... and it happens to different nics.
 
Old 03-14-2004, 09:36 PM   #7
Micah
Member
 
Registered: Apr 2002
Location: OK, USA
Distribution: Slackware64 14
Posts: 180

Original Poster
Rep: Reputation: 31
I fixed it!!! Drivers for both PCMCIA-CS and rtl8139.c...
Well... It doesn't stop working when it drops packets, instead it requests the packets again... Before it would just stall or kernel panic =)

Thanks!

These versions work:
pcmcia-cs-3.1.26
rtl8139.c v1.13
 
Old 03-14-2004, 09:42 PM   #8
ewtrowbr
LQ Newbie
 
Registered: Jan 2004
Posts: 4

Rep: Reputation: 0
I'm not a linux expert, but I know a good bit about networks. It sounds like whenever you have application traffic, your connection fails. Your nic is fine. Your driver is recent and should work.

Lemme guess... You can ping (64 byte packets) all day without problem.

Do an ifconfig and make sure your MTU is set to 1500. If it is set to anything else, IP fragmentation will fail, and you won't be able to use the internet properly. Also, check out your kernel config file to investigate any parameters that would cause IP fragmentation to fail.

The symptoms you report are generally symptoms of IP fragmentation failing, and this is usually due to MTU mismatch.

good luck.
erich
 
Old 03-15-2004, 12:31 AM   #9
Electro
Guru
 
Registered: Jan 2002
Posts: 6,042

Rep: Reputation: Disabled
You could try upgrading to 2.4 kernel version. There is a lot of improvements since 2.2 kernel version.

Try placing some switch hubs instead of just a passive hub.

Use a different netmask.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
packet loss. bruse Linux - Networking 1 09-01-2005 08:24 AM
70% packet loss bingviini Linux - Networking 5 11-18-2004 11:35 AM
50% packet loss only with Linux alexdanoob Linux - Networking 2 04-21-2004 05:24 AM
ping packet loss on FreeBSD Vyeperman *BSD 4 10-04-2003 12:58 AM
90% packet loss to router? OatBran Linux - Networking 7 11-19-2001 01:54 AM


All times are GMT -5. The time now is 03:18 AM.

Main Menu
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration