From owner-freebsd-hackers  Thu Oct 23 07:16:05 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA28701
          for hackers-outgoing; Thu, 23 Oct 1997 07:16:05 -0700 (PDT)
          (envelope-from owner-freebsd-hackers)
Received: from plum.cyber.com.au (plum.cyber.com.au [203.7.155.24])
          by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA28692
          for <hackers@freebsd.org>; Thu, 23 Oct 1997 07:16:01 -0700 (PDT)
          (envelope-from darrenr@cyber.com.au)
Received: (from darrenr@localhost) by plum.cyber.com.au (8.6.12/8.6.6) id AAA06574 for hackers@freebsd.org; Fri, 24 Oct 1997 00:15:50 +1000
From: Darren Reed <darrenr@cyber.com.au>
Message-Id: <199710231415.AAA06574@plum.cyber.com.au>
Subject: MTU Path discovery.
To: hackers@freebsd.org
Date: Fri, 24 Oct 1997 00:15:50 +1000 (EST)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


I'm want to add a sysctl knob to control this (default to on).

At present, MTU path discovery only seems to be enabled for TCP, but
I'm reluctant to make it "net.inet.tcp.mtupathdiscovery" as I don't
want to limit its scope.  However, I'm open for comments about
whether it should be ip or icmp.

I don't think the current behaviour (is on and cannot be controlled)
is all that desirable.

Darren