Update Question 14.25:

- Add non-breakeable spaces for better rendering
- Mark up literals with <literal>
- Capitalize WWW
- Remove Telco bashing
- Remove link to Sustainable Softworks since their web page is not
  accessible
- Generalize the Mac OS solution
- Remove ppp(8) version numbers
- Mark up net/tcpmssd with <filename role="port">

Reviewed by:  trhodes
Approved by:  gabor

en_US.ISO8859-1/books/faq/book.sgml

@@ -9285,7 +9285,7 @@ ATDT1234567</programlisting>
 
       <qandaentry id=PPPoEwithNAT>
         <question id="macos-win98-pppoe-freeze">
-          <para>Why do &macos; and &windows; 98 connections freeze when
+          <para>Why do &macos; and &windows;&nbsp;98 connections freeze when
             running PPPoE on the gateway?</para>
         </question>
 
@@ -9296,33 +9296,32 @@ ATDT1234567</programlisting>
             solution:</para>
 
           <para>This is due to what is called a <quote>Black Hole</quote>
-            router.  &macos; and &windows; 98 (and maybe other Microsoft OSs)
+            router.  &macos; and &windows;&nbsp;98 (and maybe other &microsoft; OSs)
             send TCP packets with a requested segment size too big to fit
-            into a PPPoE frame (MTU is 1500 by default for Ethernet)
+            into a PPPoE frame (MTU is <literal>1500</literal> by default for Ethernet)
             <emphasis>and</emphasis> have the <quote>do not
             fragment</quote> bit set (default of TCP) and the Telco router
             is not sending ICMP <quote>must fragment</quote> back to the
-            www site you are trying to load.  (Alternatively, the router is
-            sending the ICMP packet correctly, but the firewall at the www
+            WWW site you are trying to load.  (Alternatively, the router is
+            sending the ICMP packet correctly, but the firewall at the WWW
             site is dropping it.)  When the www server is sending
             you frames that do not fit into the PPPoE pipe the Telco router
             drops them on the floor and your page does not load (some
             pages/graphics do as they are smaller than a MSS.) This seems
-            to be the default of most Telco PPPoE configurations (if only
-            they knew how to program a router... sigh...)</para>
+            to be the default of most Telco PPPoE configurations.</para>
 
-          <para>One fix is to use regedit on your 95/98 boxes to add the
-            following registry entry...</para>
+          <para>One fix is to use <application>regedit</application> on your 95/98 system to add the
+            following registry entry:</para>
 
           <programlisting>HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\MaxMTU</programlisting>
 
           <para>It should be a string with a value
-            <quote>1436</quote>, as some ADSL routers are reported to
+            <literal>1436</literal>, as some ADSL routers are reported to
             be unable to deal with packets larger than this.  This
             registry key has been changed to
             <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for
-            adapter</replaceable>\MTU</literal> in &windows; 2000 and
-            becomes a DWORD.</para>
+            adapter</replaceable>\MTU</literal> in &windows;&nbsp;2000 and
+            becomes a <literal>DWORD</literal>.</para>
 
           <para>Refer to the Microsoft Knowledge Base documents <ulink
             url="http://support.microsoft.com/support/kb/articles/Q158/4/74.asp">Q158474
@@ -9332,31 +9331,27 @@ ATDT1234567</programlisting>
             </ulink> for more information on changing &windows; MTU to
             work with a NAT router.</para>
 
-          <para>Another regedit possibility under &windows; 2000 is to
+          <para>Another regedit possibility under &windows;&nbsp;2000 to
             set the
             <literal>Tcpip\Parameters\Interfaces\<replaceable>ID for
-            adapter</replaceable>\EnablePMTUBHDetect</literal> DWORD
-            to 1 as mentioned in the Microsoft document 120642
+            adapter</replaceable>\EnablePMTUBHDetect</literal> <literal>DWORD</literal>
+            to <literal>1</literal> as mentioned in the Microsoft document 120642
             mentioned above.</para>
 
           <para>Unfortunately, &macos; does not provide an interface for
-            changing TCP/IP settings. However, there is commercial software
-            available, such as OTAdvancedTuner (OT for OpenTransport, the
-            &macos; TCP/IP stack) by <ulink
-            url="http://www.softworks.com/">Sustainable Softworks</ulink>,
+            changing TCP/IP settings. However, there many commercial software
+            available
             that will allow users to customize TCP/IP settings. &macos; NAT
-            users should select <literal>ip_interface_MTU</literal> from
-            the drop-down menu, enter <literal>1450</literal> instead of
-            <literal>1500</literal> in the box, click the box next to
-            <literal>Save as Auto Configure</literal>, and click
-            <literal>Make Active</literal>.</para>
+            users should search for their MTU settings and
+            enter <literal>1450</literal> instead of
+            <literal>1500</literal>.</para>
 
-          <para>The latest version of &man.ppp.8;
-            (2.3 or greater) has an <command>enable tcpmssfixup</command>
+          <para>The &man.ppp.8;
+            has an <command>enable tcpmssfixup</command>
             command that will automatically adjust the MSS to an appropriate
             value.  This facility is enabled by default.  If you are stuck
             with an older version of &man.ppp.8;, you
-            may want to look at the <application>tcpmssd</application>
+            may want to look at the <filename role="port">net/tcpmssd</filename>
             port.</para>
         </answer>
       </qandaentry>