1.\"	$NetBSD: rump.dhcpclient.1,v 1.2 2011/01/21 09:47:00 wiz Exp $
2.\"
3.\" Copyright (c) 2011 Antti Kantee.  All rights reserved.
4.\"
5.\" Redistribution and use in source and binary forms, with or without
6.\" modification, are permitted provided that the following conditions
7.\" are met:
8.\" 1. Redistributions of source code must retain the above copyright
9.\"    notice, this list of conditions and the following disclaimer.
10.\" 2. Redistributions in binary form must reproduce the above copyright
11.\"    notice, this list of conditions and the following disclaimer in the
12.\"    documentation and/or other materials provided with the distribution.
13.\"
14.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS "AS IS" AND
15.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
16.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
17.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
18.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
19.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
20.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
21.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
22.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
23.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
24.\" SUCH DAMAGE.
25.\"
26.Dd January 20, 2011
27.Dt RUMP.DHCPCLIENT 1
28.Os
29.Sh NAME
30.Nm rump.dhcpclient
31.Nd simple dhcp client for rump kernels
32.Sh SYNOPSIS
33.Nm
34.Ar ifname
35.Sh DESCRIPTION
36The
37.Nm
38utility is a very simple DHCP client which can be used to apply
39networking configuration on one interface in a rump kernel.
40Unlike full DHCP clients,
41.Nm
42does not store leases or renew expired leases.
43The reason for this is the typical transient nature of a rump kernel.
44Additionally,
45.Nm
46does not store a DNS resolver address since a rump
47kernel may not have file system support.
48.Pp
49After having succesfully configured networking,
50.Nm
51prints out the networking configuration and lease time and exits.
52.Pp
53Since
54.Nm
55uses
56.Xr bpf 4
57to send and receive raw network packets, the server must include
58support for bpf and vfs (for opening
59.Pa /dev/bpf ) .
60Otherwise, the following diagnostic message is printed:
61.Bd -literal -offset indent
62rump.dhcpclient: bpf: Function not implemented
63.Ed
64.Sh SEE ALSO
65.Xr rump_server 1 ,
66.Xr bpf 4
67.Sh CAVEATS
68There is no easy way to release a lease.
69