From owner-freebsd-doc Sun Jan 7 10:10: 2 2001 Delivered-To: freebsd-doc@freebsd.org Received: from mta6.snfc21.pbi.net (mta6.snfc21.pbi.net [206.13.28.240]) by hub.freebsd.org (Postfix) with ESMTP id 4AC5337B402 for ; Sun, 7 Jan 2001 10:08:49 -0800 (PST) Received: from mwozniak.uniservers.com ([63.207.129.160]) by mta6.snfc21.pbi.net (Sun Internet Mail Server sims.3.5.2000.01.05.12.18.p9) with SMTP id <0G6T005KN0W6VT@mta6.snfc21.pbi.net> for doc@FreeBSD.org; Sun, 7 Jan 2001 10:04:55 -0800 (PST) Date: Sun, 07 Jan 2001 10:03:16 -0800 From: Michael Wozniak Subject: update to "Chapter 10. PPP" of "Frequently Asked Questions for FreeBSD 2.X, 3.X and 4.X" To: doc@FreeBSD.org Reply-To: mwozniak@pobox.com Message-id: <002301c078d4$1f1a6fc0$0a80a8c0@mwozniak.uniservers.com> MIME-version: 1.0 X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 Content-type: multipart/alternative; boundary="----=_NextPart_000_0024_01C07891.10F72FC0" Importance: Normal X-MSMail-Priority: Normal X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 X-Priority: 3 (Normal) Sender: owner-freebsd-doc@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0024_01C07891.10F72FC0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, you have quoted me in the FAQ reproduced below. I would like to add to the statement "the Telco router is not sending ICMP ``must fragment'' back to the www site you are trying to load" that sometimes the Telco _is_ sendind a "must fragment" back to the www site but the firewall at the www site is dropping it (also a misconfiguration.) Also, somebody reading this FAQ asked me about Win2K so I referred them to Microsoft Knowledge Base article "Q120642 - TCP/IP & NBT Configuration Parameters for Windows NT and Windows 2000" It indicated that the registry key has changed to Tcpip\Parameters\Interfaces\\MTU Lastly, if you could change the reference "MS KB" to "Microsoft Knowledge Base" with a link to http://search.support.microsoft.com/kb, that would help some people figure these things out on their own. Thanks, Mike 10.27. Why do MacOS and Windows 98 connections freeze when running PPPoE on the gateway Thanks to Michael Wozniak for figuring this out and Dan Flemming for the Mac solution: This is due to what's called a ``Black Hole'' router. MacOS and Windows 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) 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 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 to be the default of most Telco PPPoE configurations (if only they knew how to program a router... sigh...) One fix is to use regedit on your 95/98 boxes to add the following registry entry... HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Class\NetTrans\0000\Max MTU It should be a string with a value ``1450'' (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). Refer to MS KB # ``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 router. ------=_NextPart_000_0024_01C07891.10F72FC0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi, you have quoted me in the FAQ = reproduced=20 below. 
 
I would like to add to the = statement "the Telco router is not sending ICMP ``must=20 fragment''
back to the www site you are trying to = load"=20 that sometimes the Telco _is_ sendind = a=20 "must
fragment" back to the www site but the = firewall at=20 the www site is dropping it (also a=20 misconfiguration.)
 
Also, somebody reading this FAQ asked = me about=20 Win2K so I referred them to Microsoft
Knowledge Base article "Q120642=20 - TCP/IP & NBT Configuration Parameters for Windows NT and Windows=20 2000"
It indicated that the registry key has = changed to=20 Tcpip\Parameters\Interfaces\<ID for Adapter>\MTU
 
Lastly, if you could change the = reference "MS KB"=20 to "Microsoft Knowledge Base" with a link
to http://search.support.mic= rosoft.com/kb,=20 that would help some people figure these things out on = their
own.
 
Thanks, Mike

 

10.27. Why do MacOS = and Windows=20 98 connections freeze when running PPPoE on the = gateway

Thanks to Michael Wozniak <mwozniak@netcom.ca> for = figuring=20 this out and Dan Flemming <danflemming@mac.com> for = the Mac=20 solution:

This is due to what's called a ``Black Hole'' router. MacOS and = Windows 98=20 (and maybe other Microsoft OSs) send TCP packets with a requested = segment size=20 too big to fit into a PPPoE frame (MTU is 1500 by default for ethernet) = and have the ``don't fragment'' bit set (default of = TCP) and=20 the Telco router is not sending ICMP ``must fragment'' back to the www = site you=20 are trying to load. When the www server is sending you frames that don't = fit=20 into the PPPoE pipe the Telco router drops them on the floor and your = page=20 doesn't load (some pages/graphics do as they are smaller than a MSS.) = This seems=20 to be the default of most Telco PPPoE configurations (if only they knew = how to=20 program a router... sigh...)

One fix is to use regedit on your 95/98 boxes to add the following = registry=20 entry...

    HKEY_LOCAL_MACHINE\System\C= urrentControlSet\Services\Class\NetTrans\0000\MaxMTU
   = ; 

It should be a string with a value ``1450'' (more accurately it = should be=20 ``1464'' to fit TCP packets into a PPPoE frame perfectly but the = ``1450'' gives=20 you a margin of error for other IP protocols you may encounter).

Refer to MS KB # ``Q158474 - Windows TCPIP Registry Entries'' and = ``Q120642 -=20 TCPIP & NBT Configuration Parameters for Windows NT '' for more = information=20 on changing Windoze MTU to work with a FreeBSD/NAT/PPPoE=20 router.

 ------=_NextPart_000_0024_01C07891.10F72FC0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-doc" in the body of the message