os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Explain how to get around the "black hole router" problem for MacOS clients.

Browse source 
Submitted by:	Dan Flemming <danflemming@mac.com>, jedgar
This commit is contained in:
Ben Smithurst 2000-07-16 18:06:44 +00:00
parent 3869f10762
commit c3d856b07e
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=7640
2 changed files with 36 additions and 10 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

23
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.69 2000/07/11 15:42:14 ben Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.70 2000/07/11 21:36:22 ben Exp $</pubdate>
<abstract> <abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries <para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -7757,19 +7757,20 @@ have been terminated, you should ask the remote administrator
<qandaentry id=PPPoEwithNAT> <qandaentry id=PPPoEwithNAT>
<question> <question>
<para>Why do my Windows 98 connections freeze when I run PPPoE on the gateway</para> <para>Why do MacOS and Windows 98 connections freeze when running PPPoE on the gateway</para>
</question> </question>
<answer> <answer>
<para> <para>
Thanks to Michael Wozniak <email>mwozniak@netcom.ca</email> for figuring Thanks to Michael Wozniak <email>mwozniak@netcom.ca</email> for figuring
this out: this out and Dan Flemming <email>danflemming@mac.com</email> for the Mac
solution:
</para> </para>
<para> <para>
This is due to what's called a "Black Hole" router. Windows 98 (and This is due to what's called a "Black Hole" router. MacOS and Windows 98 (and
maybe other Microsoft OSs) is sending TCP packets with a requested 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 segment size too big to fit into a PPPoE frame (MTU is 1500 by default
for ethernet) <emphasis remap=bf>and</emphasis> have the "don't fragment" for ethernet) <emphasis remap=bf>and</emphasis> have the "don't fragment"
bit set (default of TCP) and the Telco router is not sending ICMP "must bit set (default of TCP) and the Telco router is not sending ICMP "must
@ -7804,6 +7805,18 @@ have been terminated, you should ask the remote administrator
FreeBSD/NAT/PPPoE router. FreeBSD/NAT/PPPoE router.
</para> </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>,
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>
</answer> </answer>
</qandaentry> </qandaentry>

23
en_US.ISO_8859-1/books/faq/book.sgml
View file

@ -13,7 +13,7 @@
</author> </author>
</authorgroup> </authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.69 2000/07/11 15:42:14 ben Exp $</pubdate> <pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.70 2000/07/11 21:36:22 ben Exp $</pubdate>
<abstract> <abstract>
<para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries <para>This is the FAQ for FreeBSD versions 2.X, 3.X, and 4.X. All entries
@ -7757,19 +7757,20 @@ have been terminated, you should ask the remote administrator
<qandaentry id=PPPoEwithNAT> <qandaentry id=PPPoEwithNAT>
<question> <question>
<para>Why do my Windows 98 connections freeze when I run PPPoE on the gateway</para> <para>Why do MacOS and Windows 98 connections freeze when running PPPoE on the gateway</para>
</question> </question>
<answer> <answer>
<para> <para>
Thanks to Michael Wozniak <email>mwozniak@netcom.ca</email> for figuring Thanks to Michael Wozniak <email>mwozniak@netcom.ca</email> for figuring
this out: this out and Dan Flemming <email>danflemming@mac.com</email> for the Mac
solution:
</para> </para>
<para> <para>
This is due to what's called a "Black Hole" router. Windows 98 (and This is due to what's called a "Black Hole" router. MacOS and Windows 98 (and
maybe other Microsoft OSs) is sending TCP packets with a requested 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 segment size too big to fit into a PPPoE frame (MTU is 1500 by default
for ethernet) <emphasis remap=bf>and</emphasis> have the "don't fragment" for ethernet) <emphasis remap=bf>and</emphasis> have the "don't fragment"
bit set (default of TCP) and the Telco router is not sending ICMP "must bit set (default of TCP) and the Telco router is not sending ICMP "must
@ -7804,6 +7805,18 @@ have been terminated, you should ask the remote administrator
FreeBSD/NAT/PPPoE router. FreeBSD/NAT/PPPoE router.
</para> </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>,
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>
</answer> </answer>
</qandaentry> </qandaentry>