-----BEGIN PGP SIGNED MESSAGE-----


>>>>> "Michael" == Michael Richardson <mcr@sandelman.ottawa.on.ca> writes:
    Michael> My firewall has started to do:

    Michael> Jan 20 10:35:20 bud /netbsd: tlp0: receive error: dribbling bit
    Michael> Jan 20 10:35:20 bud /netbsd: tlp0: receive error: CRC error
    Michael> Jan 20 10:35:22 bud /netbsd: tlp0: receive error: dribbling bit
    Michael> Jan 20 10:35:22 bud /netbsd: tlp0: receive error: CRC error

    Michael> This interface is plugged directly into a GVC ADSL modem doing
    Michael> bridged ethernet. 
    Michael> A couple of other interfaces did this for awhile, and the switch died or
    Michael> needed to be reset soon afterwards. The GVC ADSL modem has been power cycled
    Michael> already.  (As has the firewall)

    Michael> Can anyone say what this means? Clearly, there is corruption, which the CRC
    Michael> is in fact catching, but any deeper hit on the dribbling bit? This is a
    Michael> D-LINK 4-port card in a Dell Optiplex (thus the two PCI
    Michael> bridges):

  Okay, found the datasheet... dribbling bit means that I'm getting
non-integer number of bytes. Cables do not usually go bad suddendly. I wonder
if something else moved too close. Any advice welcome.

]       ON HUMILITY: to err is human. To moo, bovine.           |  firewalls  [
]   Michael Richardson, Sandelman Software Works, Ottawa, ON    |net architect[
] mcr@sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
Comment: Finger me for keys

iQCVAwUBPiw2OoqHRg3pndX9AQEKgQQAimuqN65FpVx51tKwgF0niKf64pNmaPyB
TV8bzKPhonnphqyZulBiWhuotZhh0/Ojw/qxqOtFgInDbp+sdljwGZhYDEkEaV8p
G+8ZFRzYbbNJBgQ/MxGENiKxAMffWCmfSaWA2jWDGZFr+XdiNp5QmCUm8o9E6Zzt
jSr9ueiDkYE=
=XNZY
-----END PGP SIGNATURE-----