From owner-freebsd-stable@FreeBSD.ORG Mon Jun 23 22:19:42 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id AEE0A37B401 for ; Mon, 23 Jun 2003 22:19:42 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-64-169-104-32.dsl.lsan03.pacbell.net [64.169.104.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id E256743F93 for ; Mon, 23 Jun 2003 22:19:41 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id A39A866BE5; Mon, 23 Jun 2003 22:19:41 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 8044FB84; Mon, 23 Jun 2003 22:19:41 -0700 (PDT) Date: Mon, 23 Jun 2003 22:19:41 -0700 From: Kris Kennaway To: Doug Lee , freebsd-stable@freebsd.org Message-ID: <20030624051941.GA22883@rot13.obsecurity.org> References: <20030624051121.GA478@kirk.dlee.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="7AUc2qLy4jB3hD7Z" Content-Disposition: inline In-Reply-To: <20030624051121.GA478@kirk.dlee.org> User-Agent: Mutt/1.4.1i Subject: Re: mpd VPN won't work after upgrade from 4.6-STABLE to 4.8-STABLE X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 24 Jun 2003 05:19:43 -0000 --7AUc2qLy4jB3hD7Z Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Jun 24, 2003 at 01:11:22AM -0400, Doug Lee wrote: > I upgraded a week ago from 4.6-STABLE to 4.8-STABLE, and subsequently > my mpd-based VPN ceased to function, giving me all kinds of "protocol > rejected" messages. I haven't seen any such reports lately on this > list or questions about it on freebsd-questions, so I'm wondering what > it's related to. I can provide more details on request, but I first > wanted to see if anyone knows of an issue already. This is the latest > mpd port (3.13) on both ends (FreeBSD on both ends), and I use > mpp-e128. The link claims to come up, but any traffic on it causes > protocol-reject messages and doesn't get through (pings don't return > etc.). >=20 > Thanks for any and all help. Did you try rebuilding it? mpd uses netgraph (a kernel interface), and it's possible that backwards-compatibility was broken somewhere along the way. Kris --7AUc2qLy4jB3hD7Z Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE+999sWry0BWjoQKURAjXbAKCg83gP9CBrw4r+qUnkU08PokkCuQCeKVgi y1LikO18zxMQumUSTke2Axk= =PTzN -----END PGP SIGNATURE----- --7AUc2qLy4jB3hD7Z--