From owner-freebsd-net@FreeBSD.ORG Sun Jun 16 21:03:04 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2579A95D for ; Sun, 16 Jun 2013 21:03:04 +0000 (UTC) (envelope-from bthcom@higonnet.net) Received: from smtp2-g21.free.fr (smtp2-g21.free.fr [IPv6:2a01:e0c:1:1599::11]) by mx1.freebsd.org (Postfix) with ESMTP id B731318E1 for ; Sun, 16 Jun 2013 21:03:02 +0000 (UTC) Received: from freebsd.higonnet.net (unknown [82.238.41.134]) by smtp2-g21.free.fr (Postfix) with ESMTP id 158534B018B for ; Sun, 16 Jun 2013 23:02:56 +0200 (CEST) Received: from [127.0.0.1] (unknown [192.168.4.77]) by freebsd.higonnet.net (Postfix) with ESMTP id 195C228424 for ; Sun, 16 Jun 2013 23:02:57 +0200 (CEST) Message-ID: <51BE27FF.1020502@higonnet.net> Date: Sun, 16 Jun 2013 23:02:55 +0200 From: Bernard Higonnet User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "freebsd-net@freebsd.org" Subject: Re: How to find out a VPN link has gone down (or better, come back up)? References: <51BD91E8.8060501@higonnet.net> <5DD08E44-E481-4FF9-A5A8-AFE3E341A57C@my.gd> <51BDCE49.1000207@freebsd.org> In-Reply-To: <51BDCE49.1000207@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Antivirus: avast! (VPS 130616-0, 16/06/2013), Outbound message X-Antivirus-Status: Clean X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 16 Jun 2013 21:03:04 -0000 Well it does seem to work and is the most straight-forward solution, though presumably the devd approach should work. Thanks to both! Bernard Higonnet On 16/06/2013 16:40, Julian Elischer wrote: > On 6/16/13 8:51 PM, Damien Fleuriot wrote: >> I might be wrong but wouldn't that be a job for devd ? >> >> Alternatively set a cron job every minute to reinstall the route. > > use the up/down scripts to install the routes... that's what they are for. > >> >> >> On 16 Jun 2013, at 12:22, Bernard Higonnet wrote: >> >>> I have a machine, FreeBSD 8.1-RELEASE #0, running a VPN (MPD5) server. >>> >>> Every once in a while, the link goes down, presumably because of some >>> third-party event on the network. >>> >>> When this happens, an element placed in the routing table by hand >>> disappears since the node on the VPN server to the far-off client >>> machine no longer exists (even though the entry in the routing table >>> is marked "permanent" when it does exist). When the network problem >>> goes away, the VPN link is automatically restored, but not the >>> routing table. >>> >>> Can someone tell me if there is a way to be notified that the link >>> has been restored so that I can run a script etc. to restore the >>> routing table to what I want? >>> >>> TIA >>> Bernard Higonnet >>> _______________________________________________ >>> freebsd-net@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-net >>> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >> >> > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"