From owner-freebsd-net@FreeBSD.ORG Thu Oct 20 13:29:24 2005 Return-Path: X-Original-To: freebsd-net@freebsd.org Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 494BB16A41F for ; Thu, 20 Oct 2005 13:29:24 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from mail.helenmarks.co.uk (82-68-196-20.dsl.in-addr.zen.co.uk [82.68.196.20]) by mx1.FreeBSD.org (Postfix) with ESMTP id BBBAA43D62 for ; Thu, 20 Oct 2005 13:29:23 +0000 (GMT) (envelope-from dom@helenmarks.co.uk) Received: from localhost (localhost [127.0.0.1]) by mail.helenmarks.co.uk (Postfix) with ESMTP id 47809170A7; Thu, 20 Oct 2005 14:29:22 +0100 (BST) Received: from mail.helenmarks.co.uk ([127.0.0.1]) by localhost (mail.helenmarks.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 34016-05; Thu, 20 Oct 2005 14:29:19 +0100 (BST) Received: by mail.helenmarks.co.uk (Postfix, from userid 80) id B8E1A170A5; Thu, 20 Oct 2005 14:29:19 +0100 (BST) Received: from graphicaldatacapture-ll-194.altohiway.com ([195.12.22.194]) (SquirrelMail authenticated user dom) by www.helenmarks.co.uk with HTTP; Thu, 20 Oct 2005 14:29:19 +0100 (BST) Message-ID: <3100.195.12.22.194.1129814959.squirrel@www.helenmarks.co.uk> Date: Thu, 20 Oct 2005 14:29:19 +0100 (BST) From: "Dominic Marks" To: freebsd-net@freebsd.org User-Agent: SquirrelMail/1.4.5 MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-15 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal X-Virus-Scanned: By ClamAV 0.85.1 Subject: mpd disconnect due to LCP echo not responding X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Oct 2005 13:29:24 -0000 Hello, I have a number of staff who use pptp links to VPN (Windows to FreeBSD mpd server) in to the Office. Some times when the link is busy the LCP echos won't pass over the link quickly enough and the connection will terminate. Is there anything I can do to prevent this, or at least make it less likely to happen. Options I have thought of are: Increasing the number of echos mpd waits before disconnecting. Increasing the time out for LCP echos. Using traffic shaping to prioritise the LCP traffic over other traffic. Are any of these possible, or is there another way of acheiving the same goal? Some example log output: Oct 19 15:18:38 billy mpd: [ng5] LCP: no reply to 1 echo request(s) Oct 19 15:18:48 billy mpd: [ng5] LCP: no reply to 2 echo request(s) Oct 19 15:18:58 billy mpd: [ng5] LCP: no reply to 3 echo request(s) Oct 19 15:19:08 billy mpd: [ng5] LCP: no reply to 4 echo request(s) Oct 19 15:19:18 billy mpd: [ng5] LCP: no reply to 5 echo request(s) Oct 19 15:19:18 billy mpd: [ng5] LCP: peer not responding to echo requests Thanks, Dominic Marks