From owner-freebsd-questions Sat Oct 3 00:37:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA11494 for freebsd-questions-outgoing; Sat, 3 Oct 1998 00:37:19 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from abc.xyz.net (froggy.anchorage.ptialaska.net [208.151.119.238]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA11477 for ; Sat, 3 Oct 1998 00:37:10 -0700 (PDT) (envelope-from groggy@iname.com) Received: from localhost (localhost [127.0.0.1]) by abc.xyz.net (8.8.8/8.8.8) with SMTP id XAA02621; Fri, 2 Oct 1998 23:37:38 -0800 (AKDT) (envelope-from groggy@iname.com) Date: Fri, 2 Oct 1998 23:37:38 -0800 (AKDT) From: Steve Howe X-Sender: abc@abc.xyz.net To: Stacy Olivas cc: questions@FreeBSD.ORG Subject: Re: PPP question In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Today, I was using a windows routing program to test some things out, and > sure enough, 10 minutes into the connection I started to see FCS error > messages. > My question isL > What is an FCS errr, what causes it and how can it be fixed? FCS = frame check sequence. it's used by HDLC (the layer below PPP), nothing more than a form of checksum. if it is bad, it means your frames of data are corrupt. usually a result of line noise, overruns, etc. it can be fixed by making good physical connections and by using quality hardware, with sizable buffering. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message