From owner-freebsd-net Mon May 6 14:48:39 2002 Delivered-To: freebsd-net@freebsd.org Received: from mailout04.sul.t-online.com (mailout04.sul.t-online.com [194.25.134.18]) by hub.freebsd.org (Postfix) with ESMTP id 3D6FF37B401 for ; Mon, 6 May 2002 14:48:22 -0700 (PDT) Received: from fwd07.sul.t-online.de by mailout04.sul.t-online.com with smtp id 174qLE-0000og-07; Mon, 06 May 2002 23:48:20 +0200 Received: from spirit.zuhause.stoert.net (320050403952-0001@[217.224.166.67]) by fmrl07.sul.t-online.com with esmtp id 174qLA-1WUUyGC; Mon, 6 May 2002 23:48:16 +0200 Received: from elevation.zuhause.stoert.net (elevation.zuhause.stoert.net [192.168.66.46]) by spirit.zuhause.stoert.net (8.11.6/8.11.6) with ESMTP id g46LmFR39626 for ; Mon, 6 May 2002 23:48:15 +0200 (CEST) (envelope-from corecode@elevation.zuhause.stoert.net) Received: (from corecode@localhost) by elevation.zuhause.stoert.net (8.12.3/8.12.3/Submit) id g46LmE0c058754; Mon, 6 May 2002 23:48:14 +0200 (CEST) (envelope-from corecode) Date: Mon, 6 May 2002 23:48:10 +0200 From: "Simon 'corecode' Schubert" To: net@freebsd.org Subject: Re: pptp/ppp just closing without reason Message-Id: <20020506234810.4e97f279.corecode@corecode.ath.cx> In-Reply-To: <20020506003640.7e0f743f.corecode@corecode.ath.cx> References: <20020506003640.7e0f743f.corecode@corecode.ath.cx> X-Mailer: Sylpheed version 0.7.5claws (GTK+ 1.2.10; i386-portbld-freebsd4.5) Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; boundary="X)uD7_BC6CtVqM=." X-Sender: 320050403952-0001@t-dialin.net Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --X)uD7_BC6CtVqM=. Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit hey, okay, please ignore my previous post... i sniffed around and found out that the ppp process was kill(TERM)'ed by pptp itself. wondering why this happened led to this conclusion: the pptp server is wrong configured. it's address may be `vpngw1'. it also tells `vpngw1' as peer address for the ppp session. this means that a routing loop is produced: packets that are destined for vpngw1 (peer) are tunneled to vpngw1 (tunnel endpoint). but this again means that this packed is destined for vpngw1 - the packet in turn must be tunneled. mpd rejects this by noting "would cause routing loop". freebsd itself notes that by stating "resource lock avoided" and denying routing of such packets. this was the reason pptp couldn't send GRE packets and quit without failure notice. thanks for your attention, simon -- /"\ http://corecode.ath.cx/#donate \ / \ ASCII Ribbon Campaign / \ Against HTML Mail and News --X)uD7_BC6CtVqM=. Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (FreeBSD) iD8DBQE81vodr5S+dk6z85oRAmM8AJ43LUudGHWZBKhSh7eoeQhi1Db2iQCgsw81 Vx460eyW7M1v9Jd7Xmficjk= =sxr9 -----END PGP SIGNATURE----- --X)uD7_BC6CtVqM=.-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message