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-18-2002, 10:32 PM
|
#1
|
Member
Registered: May 2001
Location: Panama City Beach, FL
Distribution: *.BSD
Posts: 113
Rep:
|
NIC Collisions
I had a netgear FA310TX I was using as my WAN adapter in my router,...it was getting a ton of collisions on it. So I took my friends advice and got an Intel Pro 100 S. Well I am still getting collisions on the WAN side. The new Intel card is giving me collisions. Not nearly as many as the netgear but the collisions are still there. Since the new Intel card has been installed, 3 hours I think, I have "collisions:141"
Is this normal? Should I be concerned?
TIA -- Jase
|
|
|
02-19-2002, 04:42 AM
|
#2
|
Senior Member
Registered: Dec 2001
Location: The Netherlands
Distribution: Ubuntu
Posts: 1,316
Rep:
|
Depending on the amount and traffic on the network and the number of machines on that network segment that could be a normal number.
This is what my server says after 12 days of uptime, there is never much network traffic on it though:
eth0: 104 collisions (100 Mbit network)
eth1: 773 collisions (10 Mbit network)
eth2: 39765 collisions (10 Mbit coax network)
The 100 Mbit network has a lot less collisions. The only one really having troubles is the coax network but I wouldn't expect much better from it anyways.
The more computers you have on the network the greater the chance of collisions. I'd say you probably wouldn't have to worry about a number like that.
|
|
|
02-19-2002, 09:16 AM
|
#3
|
Member
Registered: May 2001
Location: Panama City Beach, FL
Distribution: *.BSD
Posts: 113
Original Poster
Rep:
|
well,...after 1 full day of up time with 2 computers on my network I am getting
collisions:3583
odd?
:edit: This is a switched network I might add
|
|
|
02-19-2002, 04:54 PM
|
#4
|
LQ Guru
Registered: Aug 2001
Location: Dublin, Ireland
Distribution: Slackware
Posts: 5,700
Rep:
|
If this thing is NAT'ing, collisions are going to be more common. I don't understand the networking behind it, but the quality of the card isn't going to alleviate the problem as well as learning the snot out of IPtables.
This is what I've got:
World: eth0(3com 905)-collisions:614
LAN: eth1(SMC card using epic100 module)-collisions:7983
Uptime is just under 4 days. This is with 4 machines on the LAN, pretty minimal traffic, and under old-school 2.2.x ipchains. The collisions soar when I'm downloading say... ISOs on one of the boxen behind the NAT.
Cheers,
Finegan
|
|
|
02-19-2002, 06:25 PM
|
#5
|
Member
Registered: Jan 2002
Location: Galveston Island
Distribution: suse, redhat
Posts: 208
Rep:
|
Collisions are expected. IEEE 802.3 CSMA/CD (ETHERNET) is the protocol. CSMA = Carrier Sensed Multiple (NIC) Access. CD = Collision Detection. If one NIC is sending, all others sense carrier and are listening. If there is no carrier sensed and two NICs try to send at one time, each NIC detects the collision, and both back off and wait a random number of tics to try again. Highly simplified, but close.
|
|
|
All times are GMT -5. The time now is 11:34 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
|
|