os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Extend the bit about using DHCP so that it mentions that BPF is

Browse source 
required in the kernel for DHCP to work.

PR:		21399
Submitted by:	Dan Pelleg <dpelleg+bsd@cs.cmu.edu>,
		Eric Ogren <eogren@earthlink.net>
This commit is contained in:
Ben Smithurst 2000-09-19 17:05:47 +00:00
parent ea0a2dc2c6
commit ed2dcfcb23
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7975
2 changed files with 70 additions and 8 deletions
en_US.ISO8859-1/books/handbook/advanced-networking
chapter.sgml
en_US.ISO_8859-1/books/handbook/advanced-networking
chapter.sgml

39
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.29 2000/08/18 15:20:35 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.30 2000/09/01 21:31:46 alex Exp $
-->
<chapter id="advanced-networking">
@ -2626,9 +2626,38 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 /usr/lib/libscrypt.so@ -> libscryp
execute dhclient, and if successful, will fill in the network
configuration information automatically.</para>
<para>To have your system use DHCP to obtain network information
upon startup, edit your <filename>/etc/rc.conf</filename> to
include the following:</para>
<para>There are two things you must do to have your system use
DHCP upon startup:</para>
<itemizedlist>
<listitem>
<para>Make sure that the <devicename>bpf</devicename>
device is compiled into your kernel. To do this, add
<literal>pseudo-device bpf</literal> to your kernel
configuration file, and rebuild the kernel. For more
information about building kernels, see <xref
linkend="kernelconfig">.</para>
<para>The <devicename>bpf</devicename> device is already
part of the <filename>GENERIC</filename> kernel that is
supplied with FreeBSD, so if you don't have a custom
kernel, you shouldn't need to create one in order to get
DHCP working.</para>
<note>
<para>For those who are particularly security conscious,
you should be warned that <devicename>bpf</devicename>
is also the device that allows packet sniffers to work
correctly (although they still have to be run as
root). <devicename>bpf</devicename>
<emphasis>is</emphasis> required to use DHCP, but if
you are very sensitive about security, you probably
shouldn't add <devicename>bpf</devicename> to your
kernel in the expectation that at some point in the
future you will be using DHCP.</para>
</note>
</listitem>
<listitem>
<para>Edit your <filename>/etc/rc.conf</filename> to
include the following:</para>
<programlisting>
ifconfig_fxp0="DHCP"
@ -2649,6 +2678,8 @@ ifconfig_fxp0="DHCP"
dhcp_program="/sbin/dhclient"
dhcp_flags=""
</programlisting>
</listitem>
</itemizedlist>
<para>The DHCP server, <command>dhcpd</command>, is included
as part of the <literal>isc-dhcp2</literal> port in the ports

39
en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -1,7 +1,7 @@
<!--
The FreeBSD Documentation Project
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.29 2000/08/18 15:20:35 alex Exp $
$FreeBSD: doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v 1.30 2000/09/01 21:31:46 alex Exp $
-->
<chapter id="advanced-networking">
@ -2626,9 +2626,38 @@ lrwxr-xr-x 1 root wheel 14 Nov 8 14:27 /usr/lib/libscrypt.so@ -> libscryp
execute dhclient, and if successful, will fill in the network
configuration information automatically.</para>
<para>To have your system use DHCP to obtain network information
upon startup, edit your <filename>/etc/rc.conf</filename> to
include the following:</para>
<para>There are two things you must do to have your system use
DHCP upon startup:</para>
<itemizedlist>
<listitem>
<para>Make sure that the <devicename>bpf</devicename>
device is compiled into your kernel. To do this, add
<literal>pseudo-device bpf</literal> to your kernel
configuration file, and rebuild the kernel. For more
information about building kernels, see <xref
linkend="kernelconfig">.</para>
<para>The <devicename>bpf</devicename> device is already
part of the <filename>GENERIC</filename> kernel that is
supplied with FreeBSD, so if you don't have a custom
kernel, you shouldn't need to create one in order to get
DHCP working.</para>
<note>
<para>For those who are particularly security conscious,
you should be warned that <devicename>bpf</devicename>
is also the device that allows packet sniffers to work
correctly (although they still have to be run as
root). <devicename>bpf</devicename>
<emphasis>is</emphasis> required to use DHCP, but if
you are very sensitive about security, you probably
shouldn't add <devicename>bpf</devicename> to your
kernel in the expectation that at some point in the
future you will be using DHCP.</para>
</note>
</listitem>
<listitem>
<para>Edit your <filename>/etc/rc.conf</filename> to
include the following:</para>
<programlisting>
ifconfig_fxp0="DHCP"
@ -2649,6 +2678,8 @@ ifconfig_fxp0="DHCP"
dhcp_program="/sbin/dhclient"
dhcp_flags=""
</programlisting>
</listitem>
</itemizedlist>
<para>The DHCP server, <command>dhcpd</command>, is included
as part of the <literal>isc-dhcp2</literal> port in the ports