John, what is pump? It is not installed on my machine. I guess I feel like a lucky one, at least I am not having the packet loss that Shannon is having. But I do sympathize with the wait time on tech support. I waited for 45 min twice and hung up. Cox's PR department should say something. I mean they have that channel with those two guys showing everyone how to install the new cox cd software for windows. By the way, when you do get in touch with tech support they tell you NOT to install the cd it will mess up your machine. LOL I think that Cox should put out a letter or an e-mail or put something on that channel explaining the problems and what they are trying to do to fix it - instead of leaving us all in the dark. I guess they don't care - they got their money not to mention they just raised the price of internet to 50 something dollars up from I think 40 dollars. That's my 2 cents.
Boyd >From: John Hebert <[EMAIL PROTECTED]> > >This number of collision is normal. Ethernet is not an intelligent >protocol, >so it just blasts out packets willy-nilly, hoping to get a word in >edge-wise >before another Ethernet device does. A collision happens when two Ethernet >devices speak out at the same instant. > >The problem is something else. What does '/sbin/pump -s' say? Also, I >believe there is a dhcp log of some kind in /var/logs. What does that say? >I'll bet the problem is your ISP's dhcpd. > >John Hebert > > > -----Original Message----- > > From: Boyd Davezac [mailto:[EMAIL PROTECTED] > > Sent: Friday, February 01, 2002 2:28 AM > > To: [EMAIL PROTECTED] > > Subject: [brluglist] Cox Cable needs to give free month this month... > > > > > > Myself and several others have been having serious problems with Cox > > internet. > > > > Since they changed to 4 hour leases on ip's with dhcp, some > > of my friends > > have lost their connection entirely, while I haven't I have > > trouble loading > > webpages. I have to hit reload many many times before > > something loads. Some > > pages load fine - but most of the time it's slow. I decided > > to boot into > > Linux from Windows so I could analyze the situation. Here is > > what I found: > > > > Output from ifconfig eth0: > > > > eth0 Link encap:Ethernet HWaddr 00:A0:CC:59:4A:3D > > inet addr:68.11.208.100 Bcast:68.11.208.255 > > Mask:255.255.255.0 > > UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1 > > RX packets:7732 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4078 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:357 txqueuelen:100 > > RX bytes:2618784 (2.4 Mb) TX bytes:553814 (540.8 Kb) > > Interrupt:5 Base address:0xc800 > > > > As you can see, after transmitting 540 kb and receiving 2.4Mb > > it had 357 > > collisions. I am not a network expert and don't know what is > > causing this > > as this was not a problem before. I think the collision > > number should be > > much lower huh? > > > > I am wondering how everyone else's connection is and could > > someone tell me > > if the collisions are indeed high or is this normal? > > > > Thanks, > > > > Boyd > > > > > > _________________________________________________________________ _________________________________________________________________ Join the worlds largest e-mail service with MSN Hotmail. http://www.hotmail.com ================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================
