From owner-freebsd-questions@FreeBSD.ORG Tue Aug 5 07:13:11 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id BA96E1065678 for ; Tue, 5 Aug 2008 07:13:11 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (oldagora.rdrop.com [199.26.172.34]) by mx1.freebsd.org (Postfix) with ESMTP id 966228FC16 for ; Tue, 5 Aug 2008 07:13:11 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id m757D0Zk060276 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 5 Aug 2008 00:13:00 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.12.9/Submit) with UUCP id m757D0DV060275; Tue, 5 Aug 2008 00:13:00 -0700 (PDT) Received: from fbsd61 by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA04591; Tue, 5 Aug 08 00:00:58 PDT Date: Tue, 05 Aug 2008 00:01:25 -0700 From: perryh@pluto.rain.com To: nvass@teledomenet.gr Message-Id: <4897fac5.ydNhtLCstlaV4ICe%perryh@pluto.rain.com> References: <488fe865.x7NyNic2A5pcZPCL%perryh@pluto.rain.com> <200807311027.37878.nvass@teledomenet.gr> <48962046.334w0KWDk7nStfQ/%perryh@pluto.rain.com> <200808041620.37610.nvass@teledomenet.gr> In-Reply-To: <200808041620.37610.nvass@teledomenet.gr> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: keramida@ceid.upatras.gr, freebsd-questions@freebsd.org, derek@computinginnovations.com Subject: Re: setting the other end's TCP segment size X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Aug 2008 07:13:11 -0000 > 1) create a static ARP entry, this will create an entry to > the routing table i.e. arp -S IPADDR MACADDR > 2) modify the mtu for that destination > i.e. route change IPADDR -mtu MTU Seems to work fine :) One problem with this approach is that a hard-coded MAC address would break if the destination's MAC address changed :( but this can be scripted around by pinging the destination (to ensure that it's up, and get an arp entry "the usual way"), then reading the MAC address from the arp table. d=192.168.200.3 ping -c 1 $d && \ arp -S $d ` arp -n $d | sed -e 's/^.* at //' -e 's/ on .*$//' ` && \ route change $d -mtu 640