Debian bug report logs - #1492, boring messages

Subject: Bug#1492: upgrade to ppp-2.2 please
Reply-To: Bernd S. Brentrup <bsb@uni-muenster.de>, debian-bugs@pixar.com
Resent-From: Bernd S. Brentrup <bsb@uni-muenster.de>
Resent-To: debian-devel@pixar.com
Resent-Date: Wed, 27 Sep 1995 06:18:02 GMT
Resent-Message-ID: <debian-bugs-handler.1492.B09270613350@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: ppp
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Wed, 27 Sep 1995 06:18:02 GMT
Received: with rfc822 via encapsulated-mail; Wed, 27 Sep 1995 06:13:35 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sxpjL-0005jrC; Tue, 26 Sep 95 23:12 PDT
Received: from MAIL.UNI-MUENSTER.DE by pixar.com with SMTP id AA05209
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 26 Sep 1995 23:12:04 -0700
Received: from PPPE013.UNI-MUENSTER.DE by uni-muenster.de (AIX 3.2/UCB 5.64/4.03)
          id AA35183; Wed, 27 Sep 1995 07:12:24 +0100
Received: by bora.uni-muenster.de
	id <m0sxplh-0001B0C@bora.uni-muenster.de>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 27 Sep 95 07:14 MET
Message-Id: <m0sxplh-0001B0C@bora.uni-muenster.de>
Date: Wed, 27 Sep 95 07:14 MET
From: Bernd S. Brentrup <bsb@uni-muenster.de>
To: debian-bugs@pixar.com

PACKAGE: ppp
MAINTAINER: Ian Murdock <imurdock@debian.org>
VERSION: 2.1.2b
PACKAGE_REVISION: 1

The problem I am describing in the attached message has gone away with
ppp-2.2, I just managed to send a 4Mb file.

I got it from
	ftp://ftp.funet.fi/pub/Linux/BETA/ppp/ppp-2.2/ppp-2.2.tar.gz

It's mirrored in the US:
	ftp://ftp.cps.cmich.edu/pub/ppp/ppp-2.2/ppp-2.2.tar.gz


--Siggy

------- start of forwarded message (RFC 934 encapsulation) -------
Return-Path: <vger.rutgers.edu!owner-linux-ppp>
Received: by bora.uni-muenster.de
	id <m0sxjdt-0001AJa@bora.uni-muenster.de>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 27 Sep 95 00:42 MET
Received: from vger.rutgers.edu by uni-muenster.de (AIX 3.2/UCB 5.64/4.03)
          id AA11912; Tue, 26 Sep 1995 23:28:18 +0100
Received: (from majordomo@localhost) by vger.rutgers.edu (8.6.12/8.6.12) id LAA29077 for linux-ppp-outgoing; Tue, 26 Sep 1995 11:09:46 -0400
Message-Id: <m0sxbaq-00015uC@bora.uni-muenster.de>
In-Reply-To: <199509161656.JAA11655@netcom5.netcom.com>
References: <9509160303.AA25218@oz.sunflower.org>
	<199509161656.JAA11655@netcom5.netcom.com>
Precedence: bulk
From: "Bernd S. Brentrup" <bsb@uni-muenster.de>
Sender: vger.rutgers.edu!owner-linux-ppp
Sender: owner-linux-ppp@vger.rutgers.edu
To: linux-ppp@vger.rutgers.edu
Cc: speer@uni-muenster.de
Subject: Re: Requests by peer to terminate LCP
Date: Tue, 26 Sep 95 16:06 MET

Since I get the same message when transfering files upstream with ftp, let me
drop into this discussion. The effect is reproducible with files >300Kb (I
didn't bother to find the minimum size).

Taking into account that transferring the files in 64Kb chunks works while
subsequently sending the same data as a file brings the link down, it seems to
me like my provider's LQM (Link Quality Monitor) and pppd 2.1.2d don't agree on
the interpretation of the PPP.

I am using Kernel 1.2.13 with pppd 2.1.2d, the problem persists since the
earliest versions I have used.

- ----------------------------[Provider's log]-----------------------------
9/25-02:46:47-38813 Morning Star Technologies PPP
9/25-02:46:47-38813 Version 1.4.1.2 [8-Aug-1994 20:50:15 rs6kaix]
9/25-02:46:47-38813 /usr/etc/pppd passive log /tmp/pppd.log.bsb 128.176.20.20:128.176.20.21
9/25-02:46:50-38813 PPP connected to 128.176.20.21 on du0
9/25-02:51:46-38813 LQM: Too many Echo packets lost
9/25-02:51:46-38813 Disconnected from 128.176.20.21 (LQM failure)
9/25-02:51:52-38813 SIGHUP
- ----------------------[excerpt from /var/log/messages]-------------------
Sep 25 02:46:38 bora pppd[3030]: pppd 2.1.2 started by bsb, uid 1000
Sep 25 02:47:15 bora pppd[3031]: Connected...
Sep 25 02:47:16 bora pppd[3031]: set kernel debugging level to 0
Sep 25 02:47:16 bora pppd[3031]: Using interface ppp0
Sep 25 02:47:16 bora kernel: ppp: channel ppp0 mtu = 1500, mru = 1500
Sep 25 02:47:16 bora kernel: ppp: channel ppp0 open
Sep 25 02:47:16 bora pppd[3031]: Connect: ppp0 <--> /dev/cua1
Sep 25 02:47:17 bora pppd[3031]: local  IP address 128.176.20.21
Sep 25 02:47:17 bora pppd[3031]: remote IP address 128.176.20.20
Sep 25 02:52:21 bora pppd[3031]: LCP terminated at peer's request
Sep 25 02:52:24 bora pppd[3031]: Connection terminated.
Sep 25 02:52:24 bora pppd[3031]: set kernel debugging level to 2
Sep 25 02:52:24 bora kernel: ppp_ioctl: set debug level 2, netpacket 0
Sep 25 02:52:24 bora kernel: ppp: channel ppp0 going down for IP packets!
Sep 25 02:52:24 bora kernel: ppp: channel ppp0 closing.
Sep 25 02:52:24 bora pppd[3031]: Exit.
- -------------------------------------------------------------------------
Obviously clocks are a little bit out of sync.

- --Siggy
------- end -------

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Bernd S. Brentrup <bsb@uni-muenster.de>
Subject: Bug#1492: Acknowledgement (was: upgrade to ppp-2.2 please)
In-Reply-To: <m0sxplh-0001B0C@bora.uni-muenster.de>
References: <m0sxplh-0001B0C@bora.uni-muenster.de>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1492" or "Re: Bug#1492" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: imurdock@debian.org (Ian Murdock)
In-Reply-To: <m0t39wv-0001drC@imagine.imaginit.com>
References: <m0t39wv-0001drC@imagine.imaginit.com> <m0sxplh-0001B0C@bora.uni-muenster.de>
Subject: Bug#1492: marked as done (was: upgrade to ppp-2.2 please)

Your message dated Wed, 11 Oct 95 17:48 EST
with message-id <m0t39wv-0001drC@imagine.imaginit.com>
and subject line Bug#1492:
has caused the attached bug report to be marked as done.

It is your now responsibility to ensure that the bug report is dealt
with.

(NB: If you are a system administrator and have no idea what I'm
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Ian Jackson
(maintainer, debian-bugs)

Received: with rfc822 via encapsulated-mail; Wed, 27 Sep 1995 06:13:35 GMT
From uni-muenster.de!bsb Tue Sep 26 23:12:32 1995
Return-Path: <bsb@uni-muenster.de>
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0sxpjL-0005jrC; Tue, 26 Sep 95 23:12 PDT
Received: from MAIL.UNI-MUENSTER.DE by pixar.com with SMTP id AA05209
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Tue, 26 Sep 1995 23:12:04 -0700
Received: from PPPE013.UNI-MUENSTER.DE by uni-muenster.de (AIX 3.2/UCB 5.64/4.03)
          id AA35183; Wed, 27 Sep 1995 07:12:24 +0100
Received: by bora.uni-muenster.de
	id <m0sxplh-0001B0C@bora.uni-muenster.de>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 27 Sep 95 07:14 MET
Message-Id: <m0sxplh-0001B0C@bora.uni-muenster.de>
Date: Wed, 27 Sep 95 07:14 MET
From: Bernd S. Brentrup <bsb@uni-muenster.de>
To: debian-bugs@pixar.com
Subject: upgrade to ppp-2.2 please

PACKAGE: ppp
MAINTAINER: Ian Murdock <imurdock@debian.org>
VERSION: 2.1.2b
PACKAGE_REVISION: 1

The problem I am describing in the attached message has gone away with
ppp-2.2, I just managed to send a 4Mb file.

I got it from
	ftp://ftp.funet.fi/pub/Linux/BETA/ppp/ppp-2.2/ppp-2.2.tar.gz

It's mirrored in the US:
	ftp://ftp.cps.cmich.edu/pub/ppp/ppp-2.2/ppp-2.2.tar.gz


--Siggy

------- start of forwarded message (RFC 934 encapsulation) -------
Return-Path: <vger.rutgers.edu!owner-linux-ppp>
Received: by bora.uni-muenster.de
	id <m0sxjdt-0001AJa@bora.uni-muenster.de>
	(Debian /\oo/\ Smail3.1.29.1 #29.33); Wed, 27 Sep 95 00:42 MET
Received: from vger.rutgers.edu by uni-muenster.de (AIX 3.2/UCB 5.64/4.03)
          id AA11912; Tue, 26 Sep 1995 23:28:18 +0100
Received: (from majordomo@localhost) by vger.rutgers.edu (8.6.12/8.6.12) id LAA29077 for linux-ppp-outgoing; Tue, 26 Sep 1995 11:09:46 -0400
Message-Id: <m0sxbaq-00015uC@bora.uni-muenster.de>
In-Reply-To: <199509161656.JAA11655@netcom5.netcom.com>
References: <9509160303.AA25218@oz.sunflower.org>
	<199509161656.JAA11655@netcom5.netcom.com>
Precedence: bulk
From: "Bernd S. Brentrup" <bsb@uni-muenster.de>
Sender: vger.rutgers.edu!owner-linux-ppp
Sender: owner-linux-ppp@vger.rutgers.edu
To: linux-ppp@vger.rutgers.edu
Cc: speer@uni-muenster.de
Subject: Re: Requests by peer to terminate LCP
Date: Tue, 26 Sep 95 16:06 MET

Since I get the same message when transfering files upstream with ftp, let me
drop into this discussion. The effect is reproducible with files >300Kb (I
didn't bother to find the minimum size).

Taking into account that transferring the files in 64Kb chunks works while
subsequently sending the same data as a file brings the link down, it seems to
me like my provider's LQM (Link Quality Monitor) and pppd 2.1.2d don't agree on
the interpretation of the PPP.

I am using Kernel 1.2.13 with pppd 2.1.2d, the problem persists since the
earliest versions I have used.

- ----------------------------[Provider's log]-----------------------------
9/25-02:46:47-38813 Morning Star Technologies PPP
9/25-02:46:47-38813 Version 1.4.1.2 [8-Aug-1994 20:50:15 rs6kaix]
9/25-02:46:47-38813 /usr/etc/pppd passive log /tmp/pppd.log.bsb 128.176.20.20:128.176.20.21
9/25-02:46:50-38813 PPP connected to 128.176.20.21 on du0
9/25-02:51:46-38813 LQM: Too many Echo packets lost
9/25-02:51:46-38813 Disconnected from 128.176.20.21 (LQM failure)
9/25-02:51:52-38813 SIGHUP
- ----------------------[excerpt from /var/log/messages]-------------------
Sep 25 02:46:38 bora pppd[3030]: pppd 2.1.2 started by bsb, uid 1000
Sep 25 02:47:15 bora pppd[3031]: Connected...
Sep 25 02:47:16 bora pppd[3031]: set kernel debugging level to 0
Sep 25 02:47:16 bora pppd[3031]: Using interface ppp0
Sep 25 02:47:16 bora kernel: ppp: channel ppp0 mtu = 1500, mru = 1500
Sep 25 02:47:16 bora kernel: ppp: channel ppp0 open
Sep 25 02:47:16 bora pppd[3031]: Connect: ppp0 <--> /dev/cua1
Sep 25 02:47:17 bora pppd[3031]: local  IP address 128.176.20.21
Sep 25 02:47:17 bora pppd[3031]: remote IP address 128.176.20.20
Sep 25 02:52:21 bora pppd[3031]: LCP terminated at peer's request
Sep 25 02:52:24 bora pppd[3031]: Connection terminated.
Sep 25 02:52:24 bora pppd[3031]: set kernel debugging level to 2
Sep 25 02:52:24 bora kernel: ppp_ioctl: set debug level 2, netpacket 0
Sep 25 02:52:24 bora kernel: ppp: channel ppp0 going down for IP packets!
Sep 25 02:52:24 bora kernel: ppp: channel ppp0 closing.
Sep 25 02:52:24 bora pppd[3031]: Exit.
- -------------------------------------------------------------------------
Obviously clocks are a little bit out of sync.

- --Siggy
------- end -------

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: Bernd S. Brentrup <bsb@uni-muenster.de>
Subject: Bug#1492 acknowledged by developer (was: upgrade to ppp-2.2 please)
References: <m0t39wv-0001drC@imagine.imaginit.com> <m0sxplh-0001B0C@bora.uni-muenster.de>
In-Reply-To: <m0sxplh-0001B0C@bora.uni-muenster.de>

This is an automatic notification regarding your bug report.

Responsibility for it has been taken by one of the developers, namely
imurdock@debian.org (Ian Murdock).

You should be hearing from them with a substantive response shortly, if
you have not already done so.  If not, please contact them directly,
or email debian-bugs@pixar.com or myself.

Ian Jackson
(maintainer, debian-bugs)