From owner-freebsd-current Wed Jan 20 02:57:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id CAA13245 for freebsd-current-outgoing; Wed, 20 Jan 1999 02:57:36 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from awfulhak.org (awfulhak.force9.co.uk [195.166.136.63]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id CAA13240 for ; Wed, 20 Jan 1999 02:57:32 -0800 (PST) (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@keep.lan.Awfulhak.org [172.16.0.8]) by awfulhak.org (8.8.8/8.8.8) with ESMTP id KAA10815; Wed, 20 Jan 1999 10:57:18 GMT (envelope-from brian@Awfulhak.org) Received: from keep.lan.Awfulhak.org (brian@localhost [127.0.0.1]) by keep.lan.Awfulhak.org (8.9.2/8.9.1) with ESMTP id IAA00908; Wed, 20 Jan 1999 08:50:01 GMT (envelope-from brian@keep.lan.Awfulhak.org) Message-Id: <199901200850.IAA00908@keep.lan.Awfulhak.org> X-Mailer: exmh version 2.0.2 2/24/98 To: alk@pobox.com cc: current@FreeBSD.ORG Subject: Re: PPP data-dependent bug In-reply-to: Your message of "Fri, 15 Jan 1999 12:03:10 CST." <13983.33200.312463.1364@avalon.east> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Jan 1999 08:50:01 +0000 From: Brian Somers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > FYI, when I rcp (actually, rsync) a certain makefile (ppp -alias), I > get lots of these, and it never completes: > > Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored > Warning: CCP: deflink: Incorrect ResetAck (id 49, not 50) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 51) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 55) ignored > Warning: CCP: deflink: Unexpected ResetAck (id 55) ignored Dare I say ``you're talking to a lousy CCP/FSM implementation'' ? (your response: It's also user-ppp). Unfortunately, there aren't any interesting logs that mention the ResetReq - just logs that mention the reason behind it :-( If you're using user-ppp on the other end, you could have a look at the CCP logs there and try to match up the FSM IDs (the bit in parenthesis after the {Send,Recv}ResetReq messages). You're proabably better off using hardware compression here - if the peer can't get a reset right. -- Brian Don't _EVER_ lose your sense of humour ! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message