From owner-freebsd-stable Mon Nov 1 10:15: 4 1999 Delivered-To: freebsd-stable@freebsd.org Received: from ady.warpnet.ro (ady.warpnet.ro [194.102.224.1]) by hub.freebsd.org (Postfix) with ESMTP id 4A71614A08 for ; Mon, 1 Nov 1999 10:14:54 -0800 (PST) (envelope-from ady@warpnet.ro) Received: from localhost (ady@localhost) by ady.warpnet.ro (8.9.3/8.9.3) with ESMTP id UAA31523; Mon, 1 Nov 1999 20:20:19 +0200 (EET) (envelope-from ady@warpnet.ro) Date: Mon, 1 Nov 1999 20:20:18 +0200 (EET) From: Adrian Penisoara To: Brian Somers Cc: freebsd-stable@FreeBSD.ORG, brian@hak.lan.Awfulhak.org, brian@hak.lan.Awfulhak.org Subject: Re: MP downliks problem (was Re: PPP dying with signal 10) In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi again, On Fri, 29 Oct 1999, Adrian Penisoara wrote: > > I think I'm misunderstanding at least some of the problem. I'm > > assuming the following: You have a two-link ppp session with ppp(8) > > running in -direct mode. > > Correct up to here... > > You then reset both modems and ppp exits. > > The client dials again (twice) and has problems establishing the > > connection because no ``replies'' are sent by one side or the other. > > Nope: On one end the carriers on both links go down (for example a wire > cut) and then the links is reestablished but almost no packets get sent > through. This is fixed only with a 'down' at the control prompt. Just to let you know: I've implemented another multilink in the same configuration with MPD ver. 2.0b2 from Whistle Communications (net/mpd from ports) and everything works smooth (no problems when links go down, even when simultaneously -- everything goes back to normal when links get back online). I haven't got yet a chance to closely trace the problem, I've resorted to a workaround: sending a "down" with pppctl every half an hour. I know it's pretty dumb but at least it saves me from a lot of nerves; still this is not 100% reliable. How exactly can I help you trace this nasty bug ? Ady (@warpnet.ro) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message