From owner-freebsd-hackers@FreeBSD.ORG Sun Nov 18 02:20:18 2012 Return-Path: Delivered-To: hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id EEDC914E for ; Sun, 18 Nov 2012 02:20:18 +0000 (UTC) (envelope-from zbeeble@gmail.com) Received: from mail-la0-f54.google.com (mail-la0-f54.google.com [209.85.215.54]) by mx1.freebsd.org (Postfix) with ESMTP id 6D70C8FC0C for ; Sun, 18 Nov 2012 02:20:17 +0000 (UTC) Received: by mail-la0-f54.google.com with SMTP id j13so3677337lah.13 for ; Sat, 17 Nov 2012 18:20:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=V0jZNTSawii8rvr0bjMqqcxBno4WUk/Gi5p3zNK0Xa8=; b=QhGgxxVaU95zF++7qp3J1+sGbsu/iGi8wPkW5zOSXaevaPnJUYIWyotGduwdAFxLOO 5DAp33K5Zx+ywWUlBrMjzeTGJGrWEe54OYtBBu+pTVDBIuijZM5ZTxsKuV2RvNRWFCQP wk9SxUFe/4T5D5tWFwfpu0GS5OvT0VPD8r9TiOUNUXpUfq4ggM7xvlycmDyy+T01ZIn2 pr2G7THoN4MpeX7UHm7egI/31YneA1LRABzKgGUFG6Ne3n6mUdkHTxNd7SnX80e6kxSi fjGV0nHjwxmzElIoA9t7t8ilBapIN6Gp3QM5rhVpn6waXCWV4ZTq5NE43z6IWJY6FBii Sh7Q== MIME-Version: 1.0 Received: by 10.152.108.37 with SMTP id hh5mr8116566lab.52.1353205216719; Sat, 17 Nov 2012 18:20:16 -0800 (PST) Received: by 10.112.49.138 with HTTP; Sat, 17 Nov 2012 18:20:16 -0800 (PST) In-Reply-To: <50A8239D.3080008@egr.msu.edu> References: <50A8239D.3080008@egr.msu.edu> Date: Sat, 17 Nov 2012 21:20:16 -0500 Message-ID: Subject: Re: Jumbo Packet fail. From: Zaphod Beeblebrox To: Adam McDougall Content-Type: text/plain; charset=ISO-8859-1 Cc: hackers@freebsd.org X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Nov 2012 02:20:19 -0000 On Sat, Nov 17, 2012 at 6:54 PM, Adam McDougall wrote: > On 11/17/2012 5:32 PM, Zaphod Beeblebrox wrote: [my description of MTU not having effect on MSS, deleted] > Did you reboot or alter the existing route so it also uses the higher MTU? I > realize that need is not obvious. Check netstat -rni. O I C. I understand why it is, but it's a small surprise to me. This brings up a related issue: The syntax for things I don't do often with route and friends (I suppose I would include netstat and sometimes even ifconfig) is difficult to remember and difficult to discern. As an example, going from your first post, I might want to do something like: route change 192.168.221.84 mtu 9014 ... but this doesn't work. In fact, part of this problem is that the route doesn't have an easy to specify destination, but it's also because it's not clear how to indicate the mtu change. It's similarly hard to specify ipv6 addresses for route et. al. And the man pages are of little help here.