From owner-freebsd-current@FreeBSD.ORG  Sun May  9 15:02:13 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id B0C7F16A4CE; Sun,  9 May 2004 15:02:13 -0700 (PDT)
Received: from smtp3.sentex.ca (smtp3.sentex.ca [64.7.153.18])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 393F643D31; Sun,  9 May 2004 15:02:13 -0700 (PDT)
	(envelope-from mike@sentex.net)
Received: from avscan2.sentex.ca (avscan2.sentex.ca [199.212.134.19])
	by smtp3.sentex.ca (8.12.11/8.12.10) with ESMTP id i49M27II046234;
	Sun, 9 May 2004 18:02:07 -0400 (EDT)
	(envelope-from mike@sentex.net)
Received: from localhost (localhost [127.0.0.1])
	by avscan2.sentex.ca (Postfix) with ESMTP
	id 465DD59C8C; Sun,  9 May 2004 18:02:12 -0400 (EDT)
Received: from avscan2.sentex.ca ([127.0.0.1])
 by localhost (avscan2.sentex.ca [127.0.0.1]) (amavisd-new, port 10024)
 with SMTP id 54610-07; Sun,  9 May 2004 18:02:12 -0400 (EDT)
Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18])
	by avscan2.sentex.ca (Postfix) with ESMTP
	id 09EC959C87; Sun,  9 May 2004 18:02:12 -0400 (EDT)
Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27])
	by lava.sentex.ca (8.12.11/8.12.11) with ESMTP id i49M2AVT035114;
	Sun, 9 May 2004 18:02:10 -0400 (EDT)
	(envelope-from mike@sentex.net)
Message-Id: <6.0.3.0.0.20040509180050.04abf178@64.7.153.2>
X-Sender: mdtpop@64.7.153.2 (Unverified)
X-Mailer: QUALCOMM Windows Eudora Version 6.0.3.0
Date: Sun, 09 May 2004 18:04:38 -0400
To: Andre Oppermann <andre@freebsd.org>
From: Mike Tancsa <mike@sentex.net>
In-Reply-To: <409BFBD5.5050101@freebsd.org>
References: <6.0.3.0.0.20040507151017.08816e60@64.7.153.2>
 <409BFBD5.5050101@freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
X-Virus-Scanned: by amavisd-new
X-Virus-Scanned: by amavisd-new at (avscan2) sentex.ca
cc: freebsd-current@freebsd.org
Subject: Re: routing bug?
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 09 May 2004 22:02:13 -0000

At 05:12 PM 07/05/2004, Andre Oppermann wrote:
>I hope this explains the effect you are seeing.  A backport or MFC of

It does, and thanks very much.  For us, the problem is particularly acute 
with respect to raccoon and dynamic PtP links that come and go.  We are 
presently trying to work around it at the application layer as a move to 
CURRENT makes us a little nervous for now in production.

         ---Mike