[master] Add section on ports to client and server man pages

diff --git a/client/dhclient.8 b/client/dhclient.8
index f2f93c1970e93ba06cda24a205b7ae1a9f6f7fe3..b319c8e76b4beef433b93b38e0f7e5beb865ce5b 100644 (file)
--- a/client/dhclient.8
+++ b/client/dhclient.8
@@ -427,8 +427,33 @@ Path to the network configuration script invoked by
 when it gets a lease.  If unspecified, the default
 .B CLIENTBINDIR/dhclient-script
 is used.  See \fBdhclient-script(8)\fR for a description of this file.
+.PP
+.SH PORTS
+During operations the client may use multiple UDP ports
+to provide different functions.  Which ports are opened depends
+on both the way you compiled your code and the configuration you
+supply.  The following should provide you an idea of what
+ports may be in use.
+
+Normally a DHCPv4 client will open a raw UDP socket to receive
+and send most DHCPv4 packets.  It also opens a fallback UDP socket
+for use in sending unicast packets.  Normally these will both
+use the well known port number for BOOTPC.
+
+For DHCPv6 the client opens a UDP socket on the well known
+client port and a fallback UDP socket on a random port for
+use in sending unicast messages.  Unlike DHCPv4 the well
+known socket doesn't need to be opened in raw mode.
 
+If you have included an omapi port statement in your configuration
+file then the client will open a TCP socket on that port to
+listen for OMPAI connections.  When something connects another
+port will be used for the established connection.
 
+When DDNS is enabled at compile time (see includes/site.h)
+the client will open both a v4 and a v6 UDP socket on
+random ports.  These ports are opened even if DDNS is disabled
+in the configuration file.
 .PP
 .SH CONFIGURATION
 The syntax of the \fBdhclient.conf(5)\fR file is discussed separately.

diff --git a/server/dhcpd.8 b/server/dhcpd.8
index 103128d598ab23984f49a5acfd7794a7331a1147..bfda6397400f793a6538b10ba92bc66ef130dde6 100644 (file)
--- a/server/dhcpd.8
+++ b/server/dhcpd.8
@@ -326,6 +326,41 @@ Option to disable writing pid files.  By default the program
 will write a pid file.  If the program is invoked with this
 option it will not check for an existing server process.
 .PP
+.SH PORTS
+During operations the server may use multiple UDP and TCP ports
+to provide different functions.  Which ports are opened depends
+on both the way you compiled your code and the configuration you
+supply.  The following should provide you an idea of what
+ports may be in use.
+
+Normally a DHCPv4 server will open a raw UDP socket to receive
+and send most DHCPv4 packets.  It also opens a fallback UDP socket
+for use in sending unicast packets.  Normally these will both
+use the well known port number for BOOTPS.
+
+For each DHCPv4 failover peer you list in the configuartion file
+there will be a TCP socket listening for connections on the
+ports specififed in the configuration file.  When the peer connects
+there will be another socket for the established connection.
+For the established connection the side (primary or secondary)
+opening the connection will use a random port.
+
+For DHCPv6 the server opens a UDP socket on the well known
+dhcpv6-server port.
+
+The server opens an icmp socket for doing ping requests to check
+if addresses are in use.
+
+If you have included an omapi-port statement in your configuration
+file then the server will open a TCP socket on that port to
+listen for OMPAI connections.  When something connects another
+port will be used for the established connection.
+
+When DDNS is enabled at compile time (see includes/site.h)
+the server will open both a v4 and a v6 UDP socket on
+random ports.  These ports are opened even if DDNS is disabled
+in the configuration file.
+.PP
 .SH CONFIGURATION
 The syntax of the dhcpd.conf(5) file is discussed separately.  This
 section should be used as an overview of the configuration process,