From aaf620b292b1bf4d815d0a99f3f4d4da00c81d4a Mon Sep 17 00:00:00 2001 From: Ben Smithurst Date: Mon, 8 Jan 2001 18:36:28 +0000 Subject: [PATCH] Make a few minor changes to the question about connections freezing when using PPPoE. Submitted by: Michael Wozniak --- en_US.ISO8859-1/books/faq/book.sgml | 15 +++++++++++---- en_US.ISO_8859-1/books/faq/book.sgml | 15 +++++++++++---- 2 files changed, 22 insertions(+), 8 deletions(-) diff --git a/en_US.ISO8859-1/books/faq/book.sgml b/en_US.ISO8859-1/books/faq/book.sgml index 4ca0387d31..0d320e4e03 100644 --- a/en_US.ISO8859-1/books/faq/book.sgml +++ b/en_US.ISO8859-1/books/faq/book.sgml @@ -15,7 +15,7 @@ - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.134 2001/01/05 20:12:11 alex Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.135 2001/01/05 20:44:26 alex Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -9224,7 +9224,9 @@ ATDT1234567 and have the don't fragment bit set (default of TCP) and the Telco router is not sending ICMP must fragment 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 (more accurately it should be 1464 to fit TCP packets into a PPPoE frame perfectly but the 1450 gives you a margin of error for other IP - protocols you may encounter). + protocols you may encounter). This registry key is reported to + have moved to + Tcpip\Parameters\Interfaces\ID for adapter\MTU + in Windows 2000. - Refer to MS KB # Q158474 - Windows TCPIP Registry + Refer to Microsoft Knowledge + Base documents Q158474 - Windows TCPIP Registry Entries and Q120642 - TCPIP & NBT Configuration Parameters for Windows NT for more information on changing Windoze MTU to work with a FreeBSD/NAT/PPPoE diff --git a/en_US.ISO_8859-1/books/faq/book.sgml b/en_US.ISO_8859-1/books/faq/book.sgml index 4ca0387d31..0d320e4e03 100644 --- a/en_US.ISO_8859-1/books/faq/book.sgml +++ b/en_US.ISO_8859-1/books/faq/book.sgml @@ -15,7 +15,7 @@ - $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.134 2001/01/05 20:12:11 alex Exp $ + $FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.135 2001/01/05 20:44:26 alex Exp $ This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. @@ -9224,7 +9224,9 @@ ATDT1234567 and have the don't fragment bit set (default of TCP) and the Telco router is not sending ICMP must fragment 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 (more accurately it should be 1464 to fit TCP packets into a PPPoE frame perfectly but the 1450 gives you a margin of error for other IP - protocols you may encounter). + protocols you may encounter). This registry key is reported to + have moved to + Tcpip\Parameters\Interfaces\ID for adapter\MTU + in Windows 2000. - Refer to MS KB # Q158474 - Windows TCPIP Registry + Refer to Microsoft Knowledge + Base documents Q158474 - Windows TCPIP Registry Entries and Q120642 - TCPIP & NBT Configuration Parameters for Windows NT for more information on changing Windoze MTU to work with a FreeBSD/NAT/PPPoE