From owner-freebsd-current  Tue May 20 20:06:51 1997
Return-Path: <owner-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA13046
          for current-outgoing; Tue, 20 May 1997 20:06:51 -0700 (PDT)
Received: from austin.polstra.com (austin.polstra.com [206.213.73.10])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA13041
          for <current@freebsd.org>; Tue, 20 May 1997 20:06:45 -0700 (PDT)
Received: from austin.polstra.com (jdp@localhost)
	by austin.polstra.com (8.8.5/8.8.5) with ESMTP id UAA12824;
	Tue, 20 May 1997 20:06:09 -0700 (PDT)
Message-Id: <199705210306.UAA12824@austin.polstra.com>
To: rob@ideal.net.au
Subject: Re: IPDIVERT broken?
Newsgroups: polstra.freebsd.current
In-Reply-To: <3382525F.4FDE1853@ideal.net.au>
References: <3382525F.4FDE1853@ideal.net.au>
Organization: Polstra & Co., Seattle, WA
Cc: current@freebsd.org
Date: Tue, 20 May 1997 20:06:09 -0700
From: John Polstra <jdp@polstra.com>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

In article <3382525F.4FDE1853@ideal.net.au>,
Rob Wise  <rob@ideal.net.au> wrote:
> 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.

Yes, it was broken on April 27 by Garrett's "long-awaited
mega-massive-network-code-cleanup.  Part I."  Do a "cvs log
src/sys/sys/socketvar.h" for the gory details.
--
   John Polstra                                       jdp@polstra.com
   John D. Polstra & Co., Inc.                Seattle, Washington USA
   "Self-knowledge is always bad news."                 -- John Barth