From owner-freebsd-net Tue Mar 6 10: 3:30 2001 Delivered-To: freebsd-net@freebsd.org Received: from mx.databus.com (p101-44.acedsl.com [160.79.101.44]) by hub.freebsd.org (Postfix) with ESMTP id 8EC7537B719 for ; Tue, 6 Mar 2001 10:03:27 -0800 (PST) (envelope-from barney@mx.databus.com) Received: (from barney@localhost) by mx.databus.com (8.11.1/8.11.1) id f26I3ML68619; Tue, 6 Mar 2001 13:03:22 -0500 (EST) (envelope-from barney) Date: Tue, 6 Mar 2001 13:03:22 -0500 From: Barney Wolff To: "Sonne, Byron" Cc: "'freebsd-net@freebsd.org'" Subject: Re: mpd errors when trying to connect using MS pptp client Message-ID: <20010306130322.A68601@mx.databus.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: ; from bsonne@mtsinai.on.ca on Tue, Mar 06, 2001 at 12:50:10PM -0500 Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can you ping the host you're talking to? The log lines describe options in a single LCP request being sent, which apparently cannot be sent because there is no route for the target IP addr. Barney Wolff On Tue, Mar 06, 2001 at 12:50:10PM -0500, Sonne, Byron wrote: > Greetings all, > > When I try to connect to my FreeBSD 4.2 box (running mpd as a pptp server) > using the Win2k pptp client, I get the following error "Disconnected. Error > 619: The specified port is not connected". > > If I then look in my mpd.log, I see the following occur twice, here is one > of them: > > Mar 6 12:43:33 cleric mpd: [pptp] LCP: SendConfigReq #21 > Mar 6 12:43:33 cleric mpd: ACFCOMP > Mar 6 12:43:33 cleric mpd: PROTOCOMP > Mar 6 12:43:33 cleric mpd: MRU 1500 > Mar 6 12:43:33 cleric mpd: MAGICNUM e76a24e1 > Mar 6 12:43:33 cleric mpd: AUTHPROTO CHAP MSOFT > Mar 6 12:43:33 cleric mpd: [pptp] error writing len 27 frame to bypass: No > route to host > Mar 6 12:43:33 cleric mpd: pptp0-0: ignoring SetLinkInfo > > Of major interest to me is the second last line that contains the "No route > to host" comment. If they can start the handshake to the point where we can > get an error, then it seems to me there has to be some kind of route. I > thought perhaps my firewall rules were dropping a short packet generated in > this exchange, but tweaking the rules didn't seem to make any difference > (perhaps I didn't tweak them correctly ?) > > Can someone shed some more light on what this is trying to tell me? I'm > hoping this will help point me in the right direction so I can figure out > how to fix it. > > Regards, > Byron Sonne > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-net" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message