From owner-freebsd-net@FreeBSD.ORG Wed Dec 10 17:39:35 2003 Return-Path: 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 194D616A4CE for ; Wed, 10 Dec 2003 17:39:35 -0800 (PST) Received: from pit.databus.com (p70-227.acedsl.com [66.114.70.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id AD39843D13 for ; Wed, 10 Dec 2003 17:39:33 -0800 (PST) (envelope-from barney@pit.databus.com) Received: from pit.databus.com (localhost [127.0.0.1]) by pit.databus.com (8.12.10/8.12.10) with ESMTP id hBB1dSRL065398; Wed, 10 Dec 2003 20:39:28 -0500 (EST) (envelope-from barney@pit.databus.com) Received: (from barney@localhost) by pit.databus.com (8.12.10/8.12.10/Submit) id hBB1dSOr065397; Wed, 10 Dec 2003 20:39:28 -0500 (EST) (envelope-from barney) Date: Wed, 10 Dec 2003 20:39:28 -0500 From: Barney Wolff To: Andrea Venturoli Message-ID: <20031211013928.GA64700@pit.databus.com> References: <200312110037.hBB0bpb6066726@soth.ventu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200312110037.hBB0bpb6066726@soth.ventu> User-Agent: Mutt/1.4.1i X-Scanned-By: MIMEDefang 2.38 cc: freebsd-net@freebsd.org Subject: Re: Two ISP connections X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 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, 11 Dec 2003 01:39:35 -0000 On Thu, Dec 11, 2003 at 01:37:52AM -0500, Andrea Venturoli wrote: > ** Reply to note from Barney Wolff Wed, 10 Dec 2003 11:39:00 -0500 > > > > I don't know of anything published that does this, but it's easy to > > write a perl or shell script that pings the router at the adsl isp > > and does the necessary things when it disappears and reappears. > > Mmh, only problem is one of the ISP is famous for blocking ICMP as a whole, so no pings work. I haven't tried this > particular line yet, but I may need to use come other protocol. You can substitute anything that should get a response via isp1, and whose result can be tested easily. > > You start it from /usr/local/etc/rc.d (Hint - use nohup to keep it running). > Why nohup? Things started from /usr/local/etc/rc.d get a hup signal when rc is finished with all the startup scripts - I think. Anyway, if you don't use nohup, or a more-conventional way to daemonize what you've started, it will die mysteriously in a very short time. I've never seen anybody else use nohup for this purpose but it works just fine on both 4.x and 5.x. > > Without getting much fancier than is reasonable, existing connections > > will be dropped at switchovers. > > I can easily live with that. > > > I have a script that does similar things running here; email me if you > > want it. > > Why not! If you don't mind, the please send it to me :) http://www.databus.com/dslsec.tgz (FreeBSD lists don't allow attachments.) Anyone is welcome to use/copy/modify these scripts. For the two-isp problem, if you're using NAT, you probably have to kill natd, reconfigure it and restart it in the dslsec-gopri/gosec scripts. -- Barney Wolff http://www.databus.com/bwresume.pdf I'm available by contract or FT, in the NYC metro area or via the 'Net.