FreeBSD Bugzilla – Attachment 10708 Details for
Bug 21399
Handbook DHCP section doesn't mention bpf
Home
|
New
|
Browse
|
Search
|
[?]
|
Reports
|
Help
|
New Account
|
Log In
Remember
[x]
|
Forgot Password
Login:
[x]
[patch]
DHCP.patch
DHCP.patch (text/plain; charset=us-ascii), 3.49 KB, created by
eogren
on 2000-09-19 15:50:05 UTC
(
hide
)
Description:
DHCP.patch
Filename:
MIME Type:
Creator:
eogren
Created:
2000-09-19 15:50:05 UTC
Size:
3.49 KB
patch
obsolete
>Index: chapter.sgml >=================================================================== >RCS file: /usr/local/doctree/doc/en_US.ISO_8859-1/books/handbook/advanced-networking/chapter.sgml,v >retrieving revision 1.30 >diff -u -r1.30 chapter.sgml >--- chapter.sgml 2000/09/01 21:31:46 1.30 >+++ chapter.sgml 2000/09/19 14:40:26 >@@ -2626,29 +2626,60 @@ > 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 >+ <quote>psuedo-device bpf</quote> 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 <emphasis>GENERIC</emphasis> 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> >+ <programlisting> > ifconfig_fxp0="DHCP" >- </programlisting> >+ </programlisting> > >- <note> >- <para>Be sure to replace <literal>fxp0</literal> with the >- designation for the interface that you wish to dynamically >- configure.</para> >- </note> >+ <note> >+ <para>Be sure to replace <literal>fxp0</literal> with the >+ designation for the interface that you wish to dynamically >+ configure.</para> >+ </note> > >- <para>If you are using a different location for >- <command>dhclient</command>, or if you wish to pass additional >- flags to <command>dhclient</command>, also include the >- following (editing as necessary):</para> >+ <para>If you are using a different location for >+ <command>dhclient</command>, or if you wish to pass additional >+ flags to <command>dhclient</command>, also include the >+ following (editing as necessary):</para> > >- <programlisting> >+ <programlisting> > dhcp_program="/sbin/dhclient" > dhcp_flags="" >- </programlisting> >+ </programlisting> >+ </listitem> >+ </itemizedlist> > > <para>The DHCP server, <command>dhcpd</command>, is included > as part of the <literal>isc-dhcp2</literal> port in the ports
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Diff
View Attachment As Raw
Actions:
View
|
Diff
Attachments on
bug 21399
: 10708