diff options
| author | Roy Marples <roy@marples.name> | 2008-01-29 10:46:54 +0000 |
|---|---|---|
| committer | Roy Marples <roy@marples.name> | 2008-01-29 10:46:54 +0000 |
| commit | 0b1a8fdb7a6f2c6b80761601c316e66512020fbc (patch) | |
| tree | c8c06f5ad9f6c696244837deb6c262e5b73544c1 /dhcpcd.8.in | |
| parent | 7fcc9e648bfa464c142a6a28e2431b19ac744cdd (diff) | |
| download | dhcpcd-0b1a8fdb7a6f2c6b80761601c316e66512020fbc.tar.xz | |
Man page updates.
Diffstat (limited to 'dhcpcd.8.in')
| -rw-r--r-- | dhcpcd.8.in | 22 |
1 files changed, 11 insertions, 11 deletions
diff --git a/dhcpcd.8.in b/dhcpcd.8.in index 7614bc08..ed3b4137 100644 --- a/dhcpcd.8.in +++ b/dhcpcd.8.in @@ -22,11 +22,11 @@ .\" 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 @@ -307,17 +307,17 @@ or restart the ypbind service. .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 @@ -332,7 +332,7 @@ configuration. .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 |