Strange network problem

[Brian Densmore]

I thought the frame variable was significant. You'll notice though,
the fealnx driver for my old card notes them as errors rather than
as frame. I think there might have actually been a frame of one for the fealnx
card. The via-rhine driver is the one that would increment the frame counter.
Well, tonight I'll try out the laptop on that connection.
The hub shows it as being up and 100MB full duplex, and it is in
the same location as it has always been and was working up until
yesterday. I have been suspecting either a cable issue or a MB issue.
I just don't see how it can be a MB issue though. My laptop is working
fine on another port on the hub on a different jack in a different room.

Thanks,
Brian

> -----Original Message-----
> From: Gerald Combs 
> 
> Brian Densmore wrote:
> 
> > and ifconfig returns something like:
> > 
> > eth0      Link encap:Ethernet  HWaddr xx:xx:xx:xx:xx:xx
> >           inet addr:172.21.12.2  Bcast:172.21.12.255  
> Mask:255.255.255.0
> >           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
> >           RX packets:0 errors:0 dropped:0 overruns:0 frame:23
>                                                              ^^
> >           TX packets:193 errors:0 dropped:0 overruns:0 carrier:0
> >           collisions:0 txqueuelen:100
> >           RX bytes:0 TX bytes:6348 
> >           Interrupt:x Base address:0xxxxx
> 
> The ifconfig(8) man page doesn't say what the "frame" counter is for
> (you'd think it would after all these years), but according to the
> net-tools source code it's the output of a variable called
> "rx_frame_errors".  It looks like you have framing errors on 
> your line.
>  Lots of things could cause this, including a bad driver, NIC, cable,
> patch, or switch port.  It _might_ be due to a duplex mismatch, but in
> that situation you usually have frames come through.  A speed mismatch
> might be a possibility as well.