436c7212e6
passed to the user process for incoming packets. When the sockaddr_in is passed back to the divert socket later, use thi sas the primary interface lookup and only revert to the IP address when the name fails. This solves a long standing bug with divert sockets: When two interfaces had the same address (P2P for example) the interface "assigned" to the reinjected packet was sometimes incorect. Probably we should define a "sockaddr_div" to officially hold this extended information in teh same manner as sockaddr_dl.
158 lines
5.5 KiB
Groff
158 lines
5.5 KiB
Groff
.\" $Id: divert.4,v 1.10 1998/03/12 07:30:16 charnier Exp $
|
|
.\"
|
|
.Dd June 18, 1996
|
|
.Dt DIVERT 4
|
|
.Os FreeBSD
|
|
.Sh NAME
|
|
.Nm divert
|
|
.Nd kernel packet diversion mechanism
|
|
.Sh SYNOPSIS
|
|
.Fd #include <sys/types.h>
|
|
.Fd #include <sys/socket.h>
|
|
.Fd #include <netinet/in.h>
|
|
.Ft int
|
|
.Fn socket PF_INET SOCK_RAW IPPROTO_DIVERT
|
|
.Sh DESCRIPTION
|
|
.Pp
|
|
Divert sockets are similar to raw IP sockets, except that they
|
|
can be bound to a specific
|
|
.Nm
|
|
port via the
|
|
.Xr bind 2
|
|
system call. The IP address in the bind is ignored; only the port
|
|
number is significant.
|
|
A divert 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.
|
|
.Pp
|
|
Divert sockets are normally used in conjunction with
|
|
FreeBSD's packet filtering implementation and the
|
|
.Xr ipfw 8
|
|
program. By reading from and writing to a divert socket, matching packets
|
|
can be passed through an arbitrary ``filter'' as they travel through
|
|
the host machine, special routing tricks can be done, etc.
|
|
.Sh READING PACKETS
|
|
Packets are diverted either as they are ``incoming'' or ``outgoing.''
|
|
Incoming packets are diverted after reception on an IP interface,
|
|
whereas outgoing packets are diverted before next hop forwarding.
|
|
.Pp
|
|
Diverted packets may be read unaltered via
|
|
.Xr read 2 ,
|
|
.Xr recv 2 ,
|
|
or
|
|
.Xr recvfrom 2 .
|
|
In the latter case, the address returned will have its port set to
|
|
the divert port and the IP address set to the (first) address of
|
|
the interface on which the packet was received (if the packet
|
|
was incoming) or
|
|
.Dv INADDR_ANY
|
|
(if the packet was outgoing). In the case of an incoming packet the interface
|
|
name will also be placed in the 8 bytes following the address,
|
|
(assuming it fits).
|
|
.Sh WRITING PACKETS
|
|
Writing to a divert socket is similar to writing to a raw IP socket;
|
|
the packet is injected ``as is'' into the normal kernel IP packet
|
|
processing and minimal error checking is done.
|
|
Packets are written as either incoming or outgoing:
|
|
if
|
|
.Xr write 2
|
|
or
|
|
.Xr send 2
|
|
is used to deliver the packet, or if
|
|
.Xr sendto 2
|
|
is used with a destination IP address of
|
|
.Dv INADDR_ANY ,
|
|
then the packet is treated as if it were outgoing, i.e., destined
|
|
for a non-local address. Otherwise, the packet is assumed to be
|
|
incoming and full packet routing is done.
|
|
.Pp
|
|
In the latter case, the
|
|
IP address specified must match the address of some local interface,
|
|
or an interface name
|
|
must be found after the IP address. If an interface name is found,
|
|
that interface will be used and the value of the IP address will be
|
|
ignored (other than the fact that it is not
|
|
.Dv INADDR_ANY
|
|
).
|
|
This is to indicate on which interface the packet ``arrived.''
|
|
.Pp
|
|
Normally, packets read as incoming should be written as incoming;
|
|
similarly for outgoing packets. When reading and then writing back
|
|
packets, passing the same socket address supplied by
|
|
.Xr recvfrom 2
|
|
unmodified to
|
|
.Xr sendto 2
|
|
simplifies things.
|
|
.Sh LOOP AVOIDANCE
|
|
Packets written into a divert socket (using
|
|
.Xr sendto 2 )
|
|
are never rediverted back to the same socket. This means that a
|
|
given packet (either incoming or outgoing) will be diverted to a
|
|
given socket once and once only.
|
|
.Pp
|
|
.Xr Ipfw 8
|
|
rules are executed in order, each time the packet passes through
|
|
the kernel, but only up until a matching
|
|
.Nm
|
|
rule applies. On the second pass, after the packet has been diverted,
|
|
the divert rule is ignored and any subsequent
|
|
.Xr ipfw 8
|
|
rules are applied. For this reason, it is normally best to specify your
|
|
divert rules prior to any others.
|
|
.Sh DETAILS
|
|
To enable divert sockets, your kernel must be compiled with the option
|
|
.Dv IPDIVERT .
|
|
.Pp
|
|
If a packet is diverted but no socket is bound to the
|
|
port, or if
|
|
.Dv IPDIVERT
|
|
is not enabled in the kernel, the packet is dropped.
|
|
.Pp
|
|
Incoming packet fragments which get diverted are fully reassembled
|
|
before delivery; the diversion of any one fragment causes the entire
|
|
packet to get diverted.
|
|
If different fragments divert to different ports,
|
|
then which port ultimately gets chosen is unpredictable.
|
|
.Pp
|
|
Packets are received and sent unchanged, except that
|
|
packets written as outgoing have their IP header checksums overwritten
|
|
with the correct value.
|
|
Packets written as incoming and having incorrect checksums will be dropped.
|
|
Otherwise, all header fields are unchanged (and therefore in network order).
|
|
.Pp
|
|
Binding to port numbers less than 1024 requires super-user access, as does
|
|
creating a socket of type SOCK_RAW.
|
|
.Sh ERRORS
|
|
Writing to a divert socket can return these errors, along with
|
|
the usual errors possible when writing raw packets:
|
|
.Bl -tag -width Er
|
|
.It Bq Er EINVAL
|
|
The packet had an invalid header, or the IP options in the packet
|
|
and the socket options set were incompatible.
|
|
.It Bq Er EADDRNOTAVAIL
|
|
The destination address contained an IP address not equal to
|
|
.Dv INADDR_ANY
|
|
that was not associated with any interface.
|
|
.El
|
|
.Sh SEE ALSO
|
|
.Xr bind 2 ,
|
|
.Xr recvfrom 2 ,
|
|
.Xr sendto 2 ,
|
|
.Xr socket 2 ,
|
|
.Xr ipfw 8
|
|
.Sh BUGS
|
|
This is an attempt to provide a clean way for user mode processes
|
|
to implement various IP tricks like address translation, but it
|
|
could be cleaner, and it's too dependent on
|
|
.Xr ipfw 8 .
|
|
.Pp
|
|
It's questionable whether incoming fragments should be reassembled
|
|
before being diverted. For example, if only some fragments of a
|
|
packet destined for another machine don't get routed through the
|
|
local machine, the packet is lost. This should probably be
|
|
a settable socket option in any case.
|
|
.Sh AUTHORS
|
|
.An Archie Cobbs Aq archie@whistle.com ,
|
|
Whistle Communications Corp.
|