From owner-freebsd-current Mon Jun 10 17:07:13 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id RAA26705 for current-outgoing; Mon, 10 Jun 1996 17:07:13 -0700 (PDT) Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id RAA26700 for ; Mon, 10 Jun 1996 17:07:11 -0700 (PDT) Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id RAA05112 for current@freebsd.org; Mon, 10 Jun 1996 17:06:50 -0700 From: Terry Lambert Message-Id: <199606110006.RAA05112@phaeton.artisoft.com> Subject: New bug in de driver caused by recent changes? To: current@freebsd.org Date: Mon, 10 Jun 1996 17:06:50 -0700 (MST) X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have recently updates a machine with a new kernel (it was running a snap following the last -release. I have gotten several errors of the type: de0: receiver: CRC error When this occurs, outbound rlogin sessions get dumped (the message is a timeout of some kind). Inbound telnet sessions are undisturbed. There may be intermittent routing failures to the remote host. Is it possible that we've implemented out own version of the NT "sniper" bug? The system in questions is running routed -q. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.