From owner-freebsd-isp Fri Sep 13 8:40:10 2002 Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE30A37B400 for ; Fri, 13 Sep 2002 08:40:04 -0700 (PDT) Received: from tomts20-srv.bellnexxia.net (tomts20.bellnexxia.net [209.226.175.74]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3569E43E7B for ; Fri, 13 Sep 2002 08:40:03 -0700 (PDT) (envelope-from derek@durham.net) Received: from cerberus.motorcity.on.ca ([65.95.185.80]) by tomts20-srv.bellnexxia.net (InterMail vM.5.01.04.19 201-253-122-122-119-20020516) with ESMTP id <20020913154002.QPGP378.tomts20-srv.bellnexxia.net@cerberus.motorcity.on.ca>; Fri, 13 Sep 2002 11:40:02 -0400 Received: (from root@localhost) by cerberus.motorcity.on.ca (8.11.6/8.11.6) id g8DEoYk44861; Fri, 13 Sep 2002 10:50:34 -0400 (EDT) (envelope-from derek@durham.net) Received: from DEVELOPMENT ([192.168.254.4]) by cerberus.motorcity.on.ca (8.11.6/8.11.6av) with SMTP id g8DEoKD44853; Fri, 13 Sep 2002 10:50:20 -0400 (EDT) (envelope-from derek@durham.net) Message-ID: <001c01c25b3c$1c0b6770$04fea8c0@motorcity.on.ca> From: "Derek" To: , References: Subject: Re: nat & load balancing Date: Fri, 13 Sep 2002 11:41:55 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-Virus-Scanned: by AMaViS perl-11 ares.durham.net Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > What I was wondering is, if this can be done with a > FreeBSD box too, with 3 FE Interfaces. It could be done easily, given that what are behind the fbsd box are private IPs (10/8, 192.168/16, etc), you are not doing port forwarding (ie, hosting a web server), and that if a link fails, that termination of a TCP session is acceptable. Within this criteria you could run a cronjob that does something like if [ "`ping -c 4 [ISP1 Defaultgateway] | grep 100%`" != "" ]; then route delete default; route add default [ISP2 Defaultgateway]; fi If you wanted to get really tricky you could use some environmental variables like $CURRENT_GW, $BACKUP_GW, and swap the two when the link went down, that way when link 2 goes down, it knows to swap back to link 1. It would probably need massaging for your NAT rules as well. Derek To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message