From nobody@FreeBSD.ORG  Tue Sep 19 06:31:33 2000
Return-Path: <nobody@FreeBSD.ORG>
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id E125237B422; Tue, 19 Sep 2000 06:31:33 -0700 (PDT)
Message-Id: <20000919133133.E125237B422@hub.freebsd.org>
Date: Tue, 19 Sep 2000 06:31:33 -0700 (PDT)
From: dpelleg+bsd@cs.cmu.edu
Sender: nobody@FreeBSD.ORG
To: freebsd-gnats-submit@FreeBSD.org
Subject: Handbook DHCP section doesn't mention bpf
X-Send-Pr-Version: www-1.0

>Number:         21399
>Category:       docs
>Synopsis:       Handbook DHCP section doesn't mention bpf
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 19 06:40:01 PDT 2000
>Closed-Date:    Tue Sep 19 18:07:25 BST 2000
>Last-Modified:  Tue Sep 19 18:07:56 BST 2000
>Originator:     Dan Pelleg
>Release:        4.1
>Organization:
Carnegie Mellon University
>Environment:
>Description:
The DHCP chapter in the handbook fails to say you'll need bpf compiled into your kernel.
If you simply follow the instructions in it (like I did), it won't work. Not until you
rebuild the kernel, that is.
>How-To-Repeat:

>Fix:
Add a note to the DHCP chapter of the handbook.

>Release-Note:
>Audit-Trail:

From: Eric Ogren <eogren@earthlink.net>
To: dpelleg+bsd@cs.cmu.edu
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: docs/21399: Handbook DHCP section doesn't mention bpf
Date: Tue, 19 Sep 2000 10:47:48 -0400

 On Tue, Sep 19, 2000 at 06:31:33AM -0700, dpelleg+bsd@cs.cmu.edu wrote:
 > >Description:
 > The DHCP chapter in the handbook fails to say you'll need bpf compiled into your kernel.
 > If you simply follow the instructions in it (like I did), it won't work. Not until you
 > rebuild the kernel, that is.
 
  The attached patch should do it. I don't know if that big note about the
 bpf device I included is necessary, but both LINT and GENERIC tell the
 user to be aware of the consequences of using bpf, so I figured I might as
 well make it clear what those consequences are.
  Also, if you look at the patch, it looks like I screwed up indentation,
 but when the patch is actually applied, the indentation is correct (at
 least on my system). I have no idea why this is.
 
  And finally, just a question -- this patch turns a couple of paragraphs
 into a <listitem> within an <itemizedlist> and adjusts those paragraphs'
 indentation accordingly. Is it better to create two patches, one to make
 the paragraphs part of the list and then another with the whitespace
 change to make the section fit the style guide, or is it OK just to wrap
 the whole thing up in one patch like I did?
 
  Eric
 
 
 

From: Eric Ogren <eogren@earthlink.net>
To: dpelleg+bsd@cs.cmu.edu
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: docs/21399: Handbook DHCP section doesn't mention bpf
Date: Tue, 19 Sep 2000 10:50:05 -0400

 --ew6BAiZeqk4r7MaW
 Content-Type: text/plain; charset=us-ascii
 
 On Tue, Sep 19, 2000 at 10:47:48AM -0400, Eric Ogren wrote:
 >  The attached patch should do it. I don't know if that big note about the
 
 <sigh> 
 And now the actual patch...
 
 Eric
 
 --ew6BAiZeqk4r7MaW
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: attachment; filename="DHCP.patch"
 
 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
 
 --ew6BAiZeqk4r7MaW--
 
State-Changed-From-To: open->closed 
State-Changed-By: ben 
State-Changed-When: Tue Sep 19 18:07:25 BST 2000 
State-Changed-Why:  
Fixed, thanks! 

http://www.freebsd.org/cgi/query-pr.cgi?pr=21399 
>Unformatted:
