Errors in IFCONFIG

I just did an IFCONFIG on our squid proxy server and was amazed that we had over 6000 errors listed! I have changed the NIC, catv cable, and the port on the router (cisco catalyst 3500) and still get the errors, the lights on the router show collisions. Is there a way that I can find out what is causing the errors? This is on a Fedora Core 2 box running the latest build of squid. Its very odd because the last box did the same thing (old slackware 8) and that was the reason for building the new one. Any suggestions would be very much appreciated

Umm, not wanting to interrupt or anything, but is ifconfig the same as ipconfig?

Pretty much, IFCONFIG just gives a little more info

But ifconfig is a linux only cmd, yes?

yes ifconfig or ifcfg is for unix/linux macines only its how u configure your network hardware and find ip, mask info etc..

RD, what errors are you getting? are you getting them when you run ifconfig or are you looking at dmesg or a log file?

When I run IFCONFIG to see the stats of my network interface it shows that there has been ~1GB in traffic and of that there has now been 8000 errors and all are in TX with 0 in RX

umm getting somthing like this


eth0 Link encap:Ethernet HWaddr 00:40:05:60:71:DD
inet addr:10.40.150.1 Bcast:10.40.150.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:288 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:74789 dropped:507 overruns:0 carrier:0 coll:0
Interrupt:10 Base address:0x7000

is it working ok?

Is the server sharing it's network with something else? Have a hub or shared media connection on the same port as this server? If not, then it would sound like you are getting collisions from working in half-duplex. Might want to check the router configs. Since the problem stayed with a different server, I would check the routers configuration.

Just out of curiosity, 1gig of traffic, at 1.5k per packet, should be about 700k packets. More then that with smaller MTU.

As Daemon said, is it working okay? If it's doing what it's supposed to, it might not be as much of a problem as you think. I'm not sure if ifconfig reports it as such, but you might want to look and see if ICMP errors are picked up as TX/RX errors too. Something like a 'destination unknown'. You said you ran new cable, did you run all the tests on it, cross talk check and such? That all the errors are durring transmission, my gut tells me the NIC is running half duplex, and sending packets out when the router is sending ones in, causing collisions.

Quote:

---

Originally Posted by +Daemon+

umm getting somthing like this


eth0 Link encap:Ethernet HWaddr 00:40:05:60:71:DD
inet addr:10.40.150.1 Bcast:10.40.150.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:288 errors:0 dropped:0 overruns:0 frame:0
TX packets:86 errors:74789 dropped:507 overruns:0 carrier:0 coll:0
Interrupt:10 Base address:0x7000

is it working ok?

---

Yeah, its working OK, but not great, its a little slow for a squid box and the specs are more than enough to handle the user load that we are putting on it.