From owner-freebsd-net Wed Dec 8 7:36:16 1999 Delivered-To: freebsd-net@freebsd.org Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (Postfix) with ESMTP id 7523614D47 for ; Wed, 8 Dec 1999 07:36:10 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.3/8.9.1) with ESMTP id KAA29987; Wed, 8 Dec 1999 10:36:20 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199912081536.KAA29987@whizzo.transsys.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Steven Fletcher Cc: "'John Hay'" , net@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Very odd problem with email. References: <277A0E0FE38ED311A66A00A0C9D43A3D0781F9@data.shellnet.co.uk> In-reply-to: Your message of "Wed, 08 Dec 1999 14:30:21 GMT." <277A0E0FE38ED311A66A00A0C9D43A3D0781F9@data.shellnet.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 08 Dec 1999 10:36:19 -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hiya > > Thanks for the reply. You are somewhat correct.... just 20 minutes ago we > recived a phonecall from UUnet who told us what was going on. It was in > fact, one of the oddest problems that they've ever seen, caused by many ~'s > in the that is being transferred (belive it or not, I've verified this and > to my amazements it's true!) - it's just not getting through at the Linx. I've run into pattern sensitivity problems like this before. This is likely caused by a marginal or mis-provisioning access circuit. The encoding of '~' is 0x7e. There could be a PPP implementation problem since I think that's the async "flag" character which need to be byte-stuffed. On a leased line circuit, you might be provoking a 1's density problem on the circuit. If the CSU/DSU is configured to assume a B8ZS (rather than AMI) provisioned T-1, then it won't do anything special in the DSU when framing up the data to ensure adequate 1's density. If the circuit is actually provisioned as AMI, this could cause problems. Take a look at the CSU/DSU statistics at either end if possible, and look for line code violations, framing loss or frame slips as you try to deliver that kind of message. Depending on the direction, you might not have access to the CSU/DSU (e.g., the provider's end). louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message