Make a few minor changes to the question about connections freezing when

using PPPoE.

Submitted by:	Michael Wozniak <mwozniak@netcom.ca>
This commit is contained in:
Ben Smithurst 2001-01-08 18:36:28 +00:00
parent 5a65a99ceb
commit aaf620b292
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=8663
2 changed files with 22 additions and 8 deletions

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.134 2001/01/05 20:12:11 alex Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.135 2001/01/05 20:44:26 alex Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -9224,7 +9224,9 @@ ATDT1234567</programlisting>
<emphasis remap=bf>and</emphasis> have the <quote>don't
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. When the www server is sending
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 don't fit into the PPPoE pipe the Telco router
drops them on the floor and your page doesn't load (some
pages/graphics do as they are smaller than a MSS.) This seems
@ -9242,9 +9244,14 @@ ATDT1234567</programlisting>
(more accurately it should be <quote>1464</quote> to fit TCP
packets into a PPPoE frame perfectly but the
<quote>1450</quote> gives you a margin of error for other IP
protocols you may encounter).</para>
protocols you may encounter). This registry key is reported to
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
<para>Refer to MS KB # <quote>Q158474 - Windows TCPIP Registry
<para>Refer to <ulink
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
Entries</quote> and <quote>Q120642 - TCPIP & NBT Configuration
Parameters for Windows NT </quote> for more information on
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE

View file

@ -15,7 +15,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.134 2001/01/05 20:12:11 alex Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.135 2001/01/05 20:44:26 alex Exp $</pubdate>
<abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X.
@ -9224,7 +9224,9 @@ ATDT1234567</programlisting>
<emphasis remap=bf>and</emphasis> have the <quote>don't
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. When the www server is sending
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 don't fit into the PPPoE pipe the Telco router
drops them on the floor and your page doesn't load (some
pages/graphics do as they are smaller than a MSS.) This seems
@ -9242,9 +9244,14 @@ ATDT1234567</programlisting>
(more accurately it should be <quote>1464</quote> to fit TCP
packets into a PPPoE frame perfectly but the
<quote>1450</quote> gives you a margin of error for other IP
protocols you may encounter).</para>
protocols you may encounter). This registry key is reported to
have moved to
<literal>Tcpip\Parameters\Interfaces\<replaceable>ID for adapter</replaceable>\MTU</literal>
in Windows 2000.</para>
<para>Refer to MS KB # <quote>Q158474 - Windows TCPIP Registry
<para>Refer to <ulink
URL="http://search.support.microsoft.com/kb">Microsoft Knowledge
Base</ulink> documents <quote>Q158474 - Windows TCPIP Registry
Entries</quote> and <quote>Q120642 - TCPIP & NBT Configuration
Parameters for Windows NT </quote> for more information on
changing Windoze MTU to work with a FreeBSD/NAT/PPPoE