From owner-freebsd-stable Sat Feb 2 13:15:10 2002 Delivered-To: freebsd-stable@freebsd.org Received: from InterJet.dellroad.org (adsl-63-194-81-26.dsl.snfc21.pacbell.net [63.194.81.26]) by hub.freebsd.org (Postfix) with ESMTP id 2457937B405; Sat, 2 Feb 2002 13:15:03 -0800 (PST) Received: from arch20m.dellroad.org (arch20m.dellroad.org [10.1.1.20]) by InterJet.dellroad.org (8.9.1a/8.9.1) with ESMTP id NAA47333; Sat, 2 Feb 2002 13:13:54 -0800 (PST) Received: (from archie@localhost) by arch20m.dellroad.org (8.11.6/8.11.6) id g12LDs771403; Sat, 2 Feb 2002 13:13:54 -0800 (PST) (envelope-from archie) From: Archie Cobbs Message-Id: <200202022113.g12LDs771403@arch20m.dellroad.org> Subject: Re: mpd-netgraph problem. In-Reply-To: <15449.62243.298239.408537@trooper.velocet.net> "from David Gilbert at Jan 31, 2002 08:45:07 pm" To: David Gilbert Date: Sat, 2 Feb 2002 13:13:53 -0800 (PST) Cc: freebsd-stable@FreeBSD.ORG, freebsd-net@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG David Gilbert writes: > I'm using mpd-netgraph to attempt to connect an encrypted tunnel. It > appears to connect (according to the messages), but the following is > spit out for most packets I try to put down the tunnel: > > [vpn] LCP: rec'd Protocol Reject #1 link 0 (Opened) > [vpn] LCP: protocol 0x0029 was rejected > [vpn] LCP: rec'd Protocol Reject #2 link 0 (Opened) > [vpn] LCP: protocol 0x00a1 was rejected > > (on the one end) > > [strikeppp] rec'd unexpected protocol 0x0029 on link -1, rejecting > [strikeppp] rec'd unexpected protocol 0x00a1 on link -1, rejecting > [strikeppp] rec'd unexpected protocol 0x0001 on link -1, rejecting > > (on the other) > > The second log also contains lines of the form: > > [strikeppp] rec'd proto 0xee53 on MP link! (ignoring) > [strikeppp] rec'd proto 0xcc0d on MP link! (ignoring) > > ... any ideas? This is usually because one side is sending encrypted traffic that the other is thinking is not encrypted... i.e., it's a side-effect of a negotiation problem. I've just heard from another person with this problem. Check your logs for something like ``"enable chap" required for MPPE'' on one side. As a workaround, if you are doing CHAP in both directions, try turning it off in one direction. -Archie __________________________________________________________________________ Archie Cobbs * Packet Design * http://www.packetdesign.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message