Mention how to use net.graph.nonstandard_pppoe to enable PPPoE on

the 3Com HomeConnect ADSL Modem.

en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml

@@ -1,7 +1,7 @@
 <!--
      The FreeBSD Documentation Project
 
-     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.53 2001/09/03 02:29:27 brian Exp $
+     $FreeBSD: doc/en_US.ISO8859-1/books/handbook/ppp-and-slip/chapter.sgml,v 1.54 2001/09/03 02:29:38 brian Exp $
 -->
 
 <chapter id="ppp-and-slip">
@@ -1907,6 +1907,36 @@ ppp_profile="name_of_service_provider"</programlisting>
 	</listitem>
       </itemizedlist>
     </sect2>
+
+    <sect2>
+    <sect2 id="ppp-3com">
+
+      <title>PPPoE with a 3Com HomeConnect ADSL Modem Dual Link</title>
+
+      <para>This modem does not follow <ulink
+	url="http://www.faqs.org/rfcs/rfc2516.html">RFC 2516</ulink>
+	(<emphasis>A Method for transmitting PPP over Ethernet
+	(PPPoE)</emphasis>, written by L. Mamakos, K. Lidl, J. Evarts,
+	D. Carrel, D. Simone, and R. Wheeler).  Instead, different packet
+	type codes have been used for the Ethernet frames.  Please complain
+	to <ulink url="http://www.3com.com/">3Com</ulink> if you think it
+	should comply with the PPPoE specification.</para>
+
+      <para>In order to make FreeBSD capable of communicating with this
+	device, a sysctl must be set.  This can be done automatically at
+	boot time by updating <filename>/etc/sysctl.conf</filename>:</para>
+
+	<programlisting>net.graph.nonstandard_pppoe=1</programlisting>
+
+      <para>or can be done for immediate effect with the command
+	<command>sysctl -w net.graph.nonstandard_pppoe=1</command>.</para>
+
+      <para>Unfortunately, because this is a system-wide setting, it is
+	not possible to talk to a normal PPPoE client or server and a
+	3Com HomeConnect ADSL Modem at the same time.</para>
+
+      <para>
+    </sect2>
   </sect1>
 
   <sect1 id="slip">