From owner-freebsd-questions@FreeBSD.ORG  Tue Nov  2 02:01:30 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 58CEB16A4CE
	for <freebsd-questions@freebsd.org>;
	Tue,  2 Nov 2004 02:01:30 +0000 (GMT)
Received: from earwig.cisdata.net (uunet-42.231.cisdata.net [65.213.42.231])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 3DCA743D2D
	for <freebsd-questions@freebsd.org>;
	Tue,  2 Nov 2004 02:01:30 +0000 (GMT)
	(envelope-from mjeung@cisdata.net)
Received: from [192.168.43.200] (helo=[192.168.43.200])
	by earwig.cisdata.net with esmtp (Exim 4.30; FreeBSD)
	id 1COnzJ-000JdV-JQ
	for freebsd-questions@freebsd.org; Mon, 01 Nov 2004 18:01:33 -0800
Mime-Version: 1.0 (Apple Message framework v619)
Content-Transfer-Encoding: 7bit
Message-Id: <3617A316-2C73-11D9-87F9-000A95D02EE0@cisdata.net>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: freebsd-questions@freebsd.org
From: Michael Jeung <mjeung@cisdata.net>
Date: Mon, 1 Nov 2004 18:02:12 -0800
X-Mailer: Apple Mail (2.619)
Subject: routed on lo0 device
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Nov 2004 02:01:30 -0000

Hello everyone,

I'm trying to get past a sticky routing situation by running routed on 
all of my machines in my server cluster.  I've been instructed by 
several sources of authority that the best solution for a multi-homed 
ip address scenario is bind the ip addresses to the loopback device and 
use routed to advertise their presence.

I'm having difficulty getting routed to bind to the loopback device.  
By default, routed seems to think the loopback device should be in 
passive mode - which causes routed to completely ignore all ips 
associated with the device.  (Perhaps this is to avoid advertising 
routes to 127.0.0.1?)  In any case, I was just curious as to whether 
anyone has every dealt with a situation like this before.

Is there some sort of trick to getting routed to work with the loopback 
device?  I want the loopback device to be active for routed, not 
passive.

Thanks!

Michael Jeung