From owner-freebsd-current  Tue May 20 20:00:51 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA12845
          for current-outgoing; Tue, 20 May 1997 20:00:51 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA12840
          for <freebsd-current@FreeBSD.ORG>; Tue, 20 May 1997 20:00:48 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id TAA28197;
	Tue, 20 May 1997 19:51:50 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd028195; Wed May 21 02:51:49 1997
Message-ID: <33826326.62319AC4@whistle.com>
Date: Tue, 20 May 1997 19:51:18 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: Rob Wise <rob@ideal.net.au>
CC: freebsd-current@FreeBSD.ORG
Subject: Re: IPDIVERT broken?
References: <3382525F.4FDE1853@ideal.net.au>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Rob Wise wrote:
> 
> Hi,
> 
> Is anyone using IPDIVERT in their -current system?  I did a make world
> with source updated about 4 hours ago and it seems to be broken.  When
> compiling the kernel i get the following:
> 
> 
IPDIVERT not only appears to be broken, it actually is :)

I've not had time to do it yet, but plan to..
I fixed the apple talk  stack last week (had the same problem)


julian