From owner-freebsd-current Thu Feb 8 00:36:16 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id AAA10427 for current-outgoing; Thu, 8 Feb 1996 00:36:16 -0800 (PST) Received: from utrhcs.cs.utwente.nl (utrhcs.cs.utwente.nl [130.89.10.247]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id AAA10422 for ; Thu, 8 Feb 1996 00:36:12 -0800 (PST) Received: from myrtilos.cs.utwente.nl by utrhcs.cs.utwente.nl (SMI-8.6/csrelayMX-SVR4_1.2/RBINF) id JAA29661; Thu, 8 Feb 1996 09:34:02 +0100 Received: from curie.cs.utwente.nl by myrtilos.cs.utwente.nl (SMI-8.6/csrelay-Sol1.4/RB) id JAA14102; Thu, 8 Feb 1996 09:33:50 +0100 Received: from localhost by curie.cs.utwente.nl (SMI-8.6/SMI-SVR4) id JAA06936; Thu, 8 Feb 1996 09:33:51 +0100 To: "Adam David" cc: freebsd-current@freebsd.org Subject: Re: TCP/IP interoperability problem, workaround In-reply-to: Your message of "Wed, 07 Feb 1996 21:36:49 GMT." <199602072136.VAA24116@veda.is> Date: Thu, 08 Feb 1996 09:33:50 +0100 Message-ID: <6935.823768430@curie.cs.utwente.nl> From: Andras Olah Sender: owner-current@freebsd.org Precedence: bulk On Wed, 07 Feb 1996 21:36:49 GMT, "Adam David" wrote: > The problem that I had been experiencing with some TCP/IP connections not > working (typically manifesting as input being received but output not being > sent) can be worked around by setting the MTU to 552 on the relevant network > interface. This problem started in -current sometime around November/December > AFAIK, I have not taken serious time to track down the cause. Is it possible that some device on the path gets confused by MTU discovery? Just a wild guess... Andras On Tue, 05 Dec 1995 09:47:13 PST, "Garrett A. Wollman" wrote: > wollman 95/12/05 09:47:09 > > Modified: sys/netinet in_rmx.c ip_icmp.c ip_output.c ip_var.h > tcp_output.c tcp_subr.c tcp_var.h > Log: > Path MTU Discovery is now standard.