From owner-freebsd-questions@FreeBSD.ORG Mon Nov 20 08:14:51 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1A9BA16A40F for ; Mon, 20 Nov 2006 08:14:51 +0000 (UTC) (envelope-from nvass@teledomenet.gr) Received: from matrix.teledomenet.gr (dns1.teledomenet.gr [213.142.128.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id E3B5443D64 for ; Mon, 20 Nov 2006 08:14:35 +0000 (GMT) (envelope-from nvass@teledomenet.gr) Received: from iris ([192.168.1.71]) by matrix.teledomenet.gr (8.12.10/8.12.10) with ESMTP id kAK8ElEY026024; Mon, 20 Nov 2006 10:14:47 +0200 From: Nikos Vassiliadis To: freebsd-questions@freebsd.org Date: Mon, 20 Nov 2006 10:13:28 +0200 User-Agent: KMail/1.9.1 References: <455D6BCA.9070505@skoberne.net> In-Reply-To: <455D6BCA.9070505@skoberne.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-7" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200611201013.29012.nvass@teledomenet.gr> Cc: Gregor Likar , Nejc Skoberne Subject: Re: Restarting DSL connection without reboot? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 Nov 2006 08:14:51 -0000 On Friday 17 November 2006 09:59, Nejc Skoberne wrote: > I really don't like to reboot servers as soon as they lose DSL connectivity. > Is there any "proper" way to reset the connection (network card?) so that the > connection restores without a reboot? Yes, the proper way is enabling echo and/or lqr. This way ppp will know when the other peer is down and will try to reconnect. This way you will not have to restart anything, Check /usr/share/examples/ppp for examples and "man ppp". Set your timeouts at will. Åxcerpt from ppp manual: echo Default: Disabled. When this option is enabled, ppp will send LCP ECHO requests to the peer at the frequency defined by ``echoperiod''. Note, LQR requests will supersede LCP ECHO requests if enabled and negotiated. See ``set lqrperiod'' below for details. Prior to ppp version 3.4.2, ``echo'' was considered enabled if lqr was enabled and negotiated, otherwise it was considered dis- abled. For the same behaviour, it is now necessary to ``enable lqr echo'' rather than just ``enable lqr''. lqr Default: Disabled and Accepted. This option decides if Link Quality Requests will be sent or accepted. LQR is a protocol that allows ppp to determine that the link is down without rely- ing on the modems carrier detect. When LQR is enabled, ppp sends the QUALPROTO option (see ``set lqrperiod'' below) as part of the LCP request. If the peer agrees, both sides will exchange LQR packets at the agreed frequency, allowing detailed link quality monitoring by enabling LQM logging. If the peer does not agree, and if the ``echo'' option is enabled, ppp will send LCP ECHO requests instead. These packets pass no information of interest, but they MUST be replied to by the peer. Whether using LQR or LCP ECHO, ppp will abruptly drop the connec- tion if 5 unacknowledged packets have been sent rather than send- ing a 6th. A message is logged at the PHASE level, and any appropriate ``reconnect'' values are honoured as if the peer were responsible for dropping the connection. Refer to the ``enable echo'' command description for differences in behaviour prior to ppp version 3.4.2. HTH Nikos