This is the WIDE implementation of DHCP (Dynamic Host Configuration Protocol)
server, relay agent, and client. DHCP, which is defined by RFCs 1534, 1542,
2131, and 2132, provides information to a computer over a network about the
configuration of that network.
To use DHCP, configure your kernel with the following line added to your kernel
configuration file (/usr/src/sys/i386/conf/<YourMachine>):
pseudo-device bpfilter 4 #Berkeley packet filter
and make bpf devices in your /dev directory: /dev/bpf[1-3]:
cd /dev && ./MAKEDEV bpf1 bpf2 bpf3
Without the relay agent, the dhcpdb.relay file is needed. The DHCP
client(dhcpc) in this port supports dynamically changing /etc/resolv.conf and
hostname via DHCP infomation.
o `-r' is recreate /etc/resolv.conf
(resolv.conf file is overwritten.)
o `-n' is reset HOSTNAME
Please read more information in /usr/local/share/doc/dhcp/intro.dhcp or
intro.dhcp.jis.
Thanks to: Hirotaka TAKETA, Hajimu UMEMOTO, Tamotsu KANOH, Junichi SATOH,
Hisashi HIRAMOTO, Takeshi TAGUCHI, Keisuke INOUE, and Yoshiro MIHIRA.
WWW: http://web.sfc.wide.ad.jp/~tomy/dhcp/index-e.html
===> The following configuration options are available for wide-dhcp-1.4.0.7:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.
This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.
Approved by: portmgr (bapt)
For ports maintained by ports@FreeBSD.org, remove names and/or
e-mail addresses from the pkg-descr file that could reasonably
be mistaken for maintainer contact information in order to avoid
confusion on the part of users looking for support. As a pleasant
side effect this also avoids confusion and/or frustration for people
who are no longer maintaining those ports.
Say hello to the new "net-mgmt" category. There are probably more
ports that belong here than the ones I have identified and moved in
this, first, pass.
Approved in principle by: marcus
