Hi folks, hope someone can give me a bit of an explanation as to what is happening here..

Getting this on my IPcop router, this is the only line in the information section that shows any errors at all. I don't really know what frames mean in this context, let alone what is causing this.

RX packets:6504312 errors:0 dropped:0 overruns:0 frame:145

Anyone care to give it a shot?

You would need to read the manual to get the real answer but I'll take a swing at it. Frame apropos to Layer 2 communications usually refers to framing alignment errors. On the datalink layer, of which PPP is an example, information is sent in frames. We refer to frames instead of packets at this layer to distinguish them from L3 Network Layer packets.

When no frames are present on the L2 media, the line is idle. This means when the frame starts the receiving serial controller must have a way of getting clued to the fact that a frame is about to begin and what the first real byte is. For this reason most L2's serial protocols use the 7E flag, or 01111110, at the start and end of the frame. This is a bit sequence that can't appear in the rest of the frame data due to a process called bit-stuffing, which I'm not going into here.

A frame allignment error means that the serial controller didn't pick up on the flag, so couldn't read the frame. You can't really call it a data error, because it might not have been a real data error, it can't tell cos it couldn't delineate the frame.

As to why you are getting these, thats more difficult. Could be anything from a noisy line, although I would have expected more real errors as well, to a slipping clock, to just poor electronics on your router.

You need to look at what the timescale is for these errors appearing , if they all happened in the last 10 seconds, and continue then you have a real problem. If they don't continue, forget it you just had a line hit, if they clock up at a few every week, then also forget it, it won't be causing you any problems.

As I said, read the manual or contact the manufacturer as this might possibly mean something else.

Thx, i Guess i will have to monitor it over a while to see what happens with it, these are both new intel 10/100 Nics so i hoipe there is no problem there. Here is the updated info after letting the thing run a few days. What really confuses me is that ii seem to be getting these frame errors, yet no colissions or drops. I have noticed however, that the Frames count usually only starts climbing when my DSL modem is near it's maximum bandwidth.

eth0 Link encap:Ethernet HWaddr 00:00:00:00:00:xx
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6904026 errors:0 dropped:0 overruns:0 frame:8
TX packets:7130376 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:949274204 (905.2 Mb) TX bytes:2569764449 (2450.7 Mb)
Interrupt:11 Base address:0x8000

eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:xx
inet addr:142.173.xxx.xx Bcast:142.173.xxx.xxx Mask:255.255.240.0
UP BROADCAST NOTRAILERS RUNNING MTU:1500 Metric:1
RX packets:7138392 errors:0 dropped:0 overruns:0 frame:198
TX packets:6901144 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:2578617058 (2459.1 Mb) TX bytes:936530052 (893.1 Mb)
Interrupt:11 Base address:0xa000