From owner-freebsd-net@FreeBSD.ORG  Thu Jan 22 03:13:50 2004
Return-Path: <owner-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 67C1416A4CE
	for <net@freebsd.org>; Thu, 22 Jan 2004 03:13:50 -0800 (PST)
Received: from web21510.mail.yahoo.com (web21510.mail.yahoo.com
	[66.163.169.59])	by mx1.FreeBSD.org (Postfix) with SMTP id 912B843D2D
	for <net@freebsd.org>; Thu, 22 Jan 2004 03:13:49 -0800 (PST)
	(envelope-from actionarnie@yahoo.com)
Message-ID: <20040122111349.46405.qmail@web21510.mail.yahoo.com>
Received: from [196.33.33.52] by web21510.mail.yahoo.com via HTTP;
	Thu, 22 Jan 2004 03:13:49 PST
Date: Thu, 22 Jan 2004 03:13:49 -0800 (PST)
From: Arnie Schwartz <actionarnie@yahoo.com>
To: Brad du Plessis <bradd@cat.co.za>
In-Reply-To: <200401221247.50332.bradd@cat.co.za>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
cc: net@freebsd.org
Subject: Re: RTM_LOSING: Kernel Suspects Partitioning
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Jan 2004 11:13:50 -0000

> Has anyone come across this before, is this a bug in
> the kernel? (I assume it
> does the same thing in FreeBSD)

Not sure if this is a bug, but doing the following
shows a similar problem.

With boxes A and B as you mentioned;

Create a ppp interface manually on B using IP's like
10.1.1.1 -> 10.1.1.2.

Then setup a route on A to get to 10.1.1.2 via B's
ethernet IP address. If you now do a traceroute to
10.1.1.2 on A, it succeeds using B's IP as a gateway.

Now delete the ppp interface on B, and try the
traceroute again, you'll notice that it now uses B's
default gateway.

Create the ppp interface on B the same as before, and
do the traceroute on A again, you'll find that it will
still use the default gateway, even though the route
to 10.1.1.2 via 10.1.1.1 was setup by adding the ppp
interface.

This looks similar to your problem, could be a bug?

Arnie

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!
http://webhosting.yahoo.com/ps/sb/