Browse files

OpenBSD 2.9

  • Loading branch information...
1 parent b89f891 commit d8edac3a45a38077c2ae09d9ecd1e7815f6652c4 itojun committed Jul 4, 2001
Showing with 304 additions and 475 deletions.
  1. +11 −80 openbsd/usr.sbin/inetd/inetd.8
  2. +293 −395 openbsd/usr.sbin/inetd/inetd.c
@@ -30,7 +30,7 @@
.\" from: @(#)inetd.8 6.7 (Berkeley) 3/16/91
-.\" $Id: inetd.8,v 1.15 2000/04/15 02:15:18 aaron Exp $
+.\" $Id: inetd.8,v 1.18 2001/01/29 11:38:32 deraadt Exp $
.Dd March 16, 1991
@@ -62,8 +62,7 @@ Essentially,
allows running one daemon to invoke several others,
reducing load on the system.
-The option available for
-.Nm inetd:
+The options are as follows:
.Bl -tag -width Ds
.It Fl d
Turns on debugging.
@@ -252,7 +251,7 @@ spawned from
within an interval of 60 seconds.
When omitted,
.Dq max
-defaults to 40.
+defaults to 256.
Stream servers are usually marked as
.Dq nowait
@@ -335,72 +334,18 @@ creates a file
.Em /var/run/
that contains its process identifier.
.Ss IPv6 TCP/UDP behavior
-If you run servers for IPv4 and IPv6 traffic, you'll need to specify
-.Dq tcp4
-.Dq tcp6
-properly on the
-.Pa inetd.conf
-For safety reasons the author recommends you to run
-two separate process for the same server program,
-specified as two separate lines on
+If you wish to run a server for IPv4 and IPv6 traffic,
+you'll need to run two separate process for the same server program,
+specified as two separate lines on
.Pa inetd.conf ,
-.Dq tcp6
+.Dq tcp4
-.Dq tcp4 .
-For detailed description please read on.
-The behavior of
-socket is documented in RFC2553.
-Basically, it says as follows:
-.Bl -bullet -compact
-Specific bind on
-.Xr bind 2
-with address specified
-should accept IPv6 traffic to that address only.
-If you perform wildcard bind
-.Xr bind 2
-to IPv6 address
-.Li ::
-.Pc ,
-and there is no wildcard bind
-socket on that TCP/UDP port, IPv6 traffic as well as IPv4 traffic
-should be routed to that
-IPv4 traffic should be seen as if it came from IPv6 address like
-.Li ::ffff: .
-This is called IPv4 mapped address.
-If there are both wildcard bind
-socket and wildcard bind
-socket on one TCP/UDP port, they should behave separately.
-IPv4 traffic should be routed to
-socket and IPv6 should be routed to
+.Dq tcp6 .
-Because of this,
+Under various combination of IPv4/v6 daemon settings,
-will behave as follows.
+will behave as follows:
.Bl -bullet -compact
If you have only one server on
@@ -419,22 +364,8 @@ and IPv6 traffic will go to server on
If you have only one server on
.Dq tcp6 ,
-Both IPv4 and IPv6 traffic will be routed to the server.
+only IPv6 traffic will be routed to the server.
-The author do not recommend the third option on the above bullets.
-RFC2553 does not define the constraint between the order of
-.Xr bind 2 ,
-nor how IPv4 TCP/UDP port number and IPv6 TCP/UDP port number
-relate each other
-should they be integrated or separated
-.Pc .
-Implemented behavior is very different across kernel to kernel.
-Many of the servers do not properly handle IPv4 mapped address.
-Therefore, it is unwise to rely too much upon the behavior of
-wildcard bind socket.
Host address specifiers, while they make conceptual sense for RPC
services, do not work entirely correctly.
Oops, something went wrong.

0 comments on commit d8edac3

Please sign in to comment.