.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"
-.Dd Jan 28, 2008
+.Dd Jan 29, 2008
.Dt DHCPCD 8 SMM
.Sh NAME
.Nm dhcpcd
-.Nd an RFC2131 compliant DHCP client
+.Nd an RFC 2131 compliant DHCP client
.Sh SYNOPSIS
.Nm
.Op Fl dknpAEGHMLNRSTY
.Sh NOTES
Because
.Nm
-supports InfiniBand, we put a Node-specific Client Identifier or DUID in the
+supports InfiniBand, we put a Node-specific Client Identifier in the
ClientID field. This is required by RFC 4390. It's also required for DHCP IPv6
which
.Nm
-should support one day. However, some DHCP servers have no idea what a DUID is
-and reject the message. Of course, RFC 2131 allowed for future use of the
-ClientID field and this is a future use. Also, some DHCP server configurations
-require an ethernet hardware address of 6 hexacdecimal numbers in the ClientID
-which is the default behaviour of most other DHCP clients. If your DHCP server
-is as desribed above, you should fix the server, or if that is not an option
-you can compile DUID support out of
+should support one day. However, some DHCP servers have no idea what this is
+and reject the message as they do not understand type 255. This is not
+conformant with RFC 2132 and the server should be fixed. Also, some DHCP
+server configurations require an ethernet hardware address of 6 hexacdecimal
+numbers in the ClientID which is the default behaviour of most other DHCP
+clients. If your DHCP server is as desribed above, you should fix the server,
+or if that is not an option you can compile DUID support out of
.Nm
or use the
.Fl I , -clientid Ar clientid
.Pp
.Nm
requires a Berkley Packet Filter, or BPF device on BSD based systems and a
-Packet Socket on Linux based systems.
+Linux Socket Filter, or LPF device on Linux based systems.
.Sh FILES
.Bl -ohang
.It Pa @PREFIX@/etc/dhcpcd.sh