From owner-freebsd-hackers  Thu Jan 16 18:21:11 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id SAA03639
          for hackers-outgoing; Thu, 16 Jan 1997 18:21:11 -0800 (PST)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id SAA03634
          for <freebsd-hackers@FreeBSD.ORG>; Thu, 16 Jan 1997 18:21:03 -0800 (PST)
Received: from current1.whistle.com (current1.whistle.com [207.76.205.22])
          by alpo.whistle.com (8.8.4/8.8.4) with SMTP
	  id SAA24897; Thu, 16 Jan 1997 18:12:42 -0800 (PST)
Message-ID: <32DEDFC8.41C67EA6@whistle.com>
Date: Thu, 16 Jan 1997 18:11:20 -0800
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: Brian Somers <brian@awfulhak.demon.co.uk>
CC: "Daniel O'Callaghan" <danny@panda.hilink.com.au>,
        Archie Cobbs <archie@whistle.com>, freebsd-hackers@FreeBSD.ORG
Subject: Re: FreeBSD as an ISDN Router
References: <199701162136.VAA01513@awfulhak.demon.co.uk>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Brian Somers wrote:

> At this stage I'd tend to rename the "aliasing" stuff to the "masquerading" stuff - it's less likely to get confused with interface aliasing.
> 
> So, any objections to this ?
make it a port / package first.....
then it can be tested more..

> 
> BTW, where's the divert(4) page ?  I havn't got it in 3.0-current as of yesterday.  I only found some info in the ipfw page.

it just comes up for me...
man 4 divert
DIVERT(4)                 FreeBSD Programmer's Manual               
DIVERT(4)

NAME
     divert - kernel packet diversion mechanism

SYNOPSIS
     #include <sys/socket.h>
     #include <netinet/in.h>

     int
     socket(PF_INET, SOCK_RAW, IPPROTO_DIVERT)

DESCRIPTION
     Divert sockets are similar to raw IP sockets, except that they can
be
     bound to a specific divert port via the bind(2) system call. The IP
ad-
     dress in the bind is ignored; only the port number is significant. 
A di-
     vert socket bound to a divert port will receive all packets
diverted to
     that port by some (here unspecified) kernel mechanism(s).  Packets
may
     also be written to a divert port, in which case they re-enter
kernel IP
     packet processing.

     Divert sockets are normally used in conjunction with FreeBSD's
packet
     filtering implementation and the ipfw(8) program. By reading from
and
     writing to a divert socket, matching packets can be passed through
an ar-
     bitrary ``filter'' as they travel through the host machine, special
rout-
     ing tricks can be done, etc.


etc.
it's in the tree....

> 
> --
> Brian <brian@awfulhak.demon.co.uk>, <brian@freebsd.org>
>       <http://www.awfulhak.demon.co.uk/>
> Don't _EVER_ lose your sense of humour....