From owner-freebsd-net@FreeBSD.ORG Fri Feb 3 19:33:45 2006 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 49FEB16A420 for ; Fri, 3 Feb 2006 19:33:45 +0000 (GMT) (envelope-from matt@tablexi.com) Received: from mx.tablexi.com (mx.tablexi.com [69.36.39.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6ECD043D48 for ; Fri, 3 Feb 2006 19:33:44 +0000 (GMT) (envelope-from matt@tablexi.com) Received: (qmail 18435 invoked by uid 89); 3 Feb 2006 19:33:43 -0000 Received: from unknown (HELO ?127.0.0.1?) (matt@tablexi.com@64.81.143.189) by mx.tablexi.com with SMTP; 3 Feb 2006 19:33:43 -0000 Message-ID: <43E3B018.3080301@tablexi.com> Date: Fri, 03 Feb 2006 13:33:44 -0600 From: Matthew Lineen User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: freebsd 6.0 network card / route fail over question 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: Fri, 03 Feb 2006 19:33:45 -0000 Hello, I'm trying to workout the specifics of NIC/route fail over on FreeBSD 6.0 and hoped someone here could point me in the right direction. We have 2 ServerIron load balancers and each of our application servers is plugged into both LBs. So, for example, an app server would have the following... bge0 IP of x.y.z.61 netmask 255.255.255.128 bge1 IP of x.y.z.63 netmask 255.255.255.128 In /etc/rc.conf the default route is x.y.z.1 In the routing table, the default route uses Netif bge0. So, when we turn off the first load balancer, bge0 goes down, but the default route never "moves" from bge0. I assume this is because ... #1 - FreeBSD doesn't like having two interfaces bound to the same x.y.z/25 network (we get plenty of the "arp: x.y.z.123 is on bge0 but got reply from ... on bge1" messages) #2 - The default route is bound to bge0 because bge0 is the first interface that contains an IP in the same network as the default route's. So, my question is: what approaches do people take to solve this problem? I've come across forwarding and carp, but I thought I'd ask the list to see if there is something simple I'm missing, other ways of handling this, etc... Thanks, Matthew