Complete.Org: Mailing Lists: Archives: discussion: October 2001:
[aclug-L] Re: packet collisions(not package..sorry)
Home

[aclug-L] Re: packet collisions(not package..sorry)

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: discussion@xxxxxxxxx
Subject: [aclug-L] Re: packet collisions(not package..sorry)
From: Jonathan Hall <jonhall@xxxxxxxxxxxx>
Date: Wed, 31 Oct 2001 16:58:38 -0600
Reply-to: discussion@xxxxxxxxx

Collisions have nothing, really, to do with your computer at all.  The
"solution" is to get a switch instead of a hub.

A collition on an ethernet network just means that two computers tried to
talk at the same time.  When that happens, they both wait a short time (less
than a second) and retransmit the information.

If you have a large network, the number of collitions you get will go up...
unless you get a switch which helps prevent colltions (and thus improves
performance greatly)


On Wed, Oct 31, 2001 at 01:47:51PM -0800, Maverick wrote:
> 
> Hi, all
>    I found out my linux box, which has two network
> interface cards got a lot of packet collisions. One
> for internal LAN(eth1),and another for my cable
> modem(eth0).
> 
> eth0      Link encap:Ethernet  HWaddr
> 00:E0:29:54:EE:34
>           inet addr:24.254.17.106  Bcast:24.254.17.255
>  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500 
> Metric:1
>           RX packets:737349 errors:2 dropped:0
> overruns:0 frame:21
>           TX packets:133467 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:3859 txqueuelen:100
>           Interrupt:11 Base address:0x250
> Memory:c8000-ca000
> 
> eth1      Link encap:Ethernet  HWaddr
> 00:A0:24:91:CE:37
>           inet addr:192.168.1.1  Bcast:192.168.1.255 
> Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500 
> Metric:1
>           RX packets:151897 errors:7 dropped:0
> overruns:10 frame:7
>           TX packets:196801 errors:0 dropped:0
> overruns:0 carrier:1
>           collisions:8135 txqueuelen:100
>           Interrupt:10 Base address:0x300
> 
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:2669 errors:0 dropped:0
> overruns:0 frame:0
>           TX packets:2669 errors:0 dropped:0
> overruns:0 carrier:0
>           collisions:0 txqueuelen:0
> 
> Does it mean my network card has problem? or the
> network(my machine) too slow to handle the network,
> the machine is just a 486 with 14M ram and 38M swap
> space.
> Thanks
> 
> Mav
> 
> 
> 
> __________________________________________________
> Do You Yahoo!?
> Make a great connection at Yahoo! Personals.
> http://personals.yahoo.com
> -- This is the discussion@xxxxxxxxx list.  To unsubscribe,
> visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi

--
--
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
  Jonathan Hall  *  jonhall@xxxxxxxxxxxx  *  PGP public key available
 Systems Admin, Future Internet Services; Goessel, KS * (620) 367-2487
         http://www.futureks.net/  *  PGP Key ID: FE 00 FD 51
                  -=  Running Debian GNU/Linux  =-
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-- This is the discussion@xxxxxxxxx list.  To unsubscribe,
visit http://tmp2.complete.org/cgi-bin/listargate-aclug.cgi


[Prev in Thread] Current Thread [Next in Thread]