From owner-freebsd-net@FreeBSD.ORG Mon Aug 19 07:00:02 2013 Return-Path: Delivered-To: freebsd-net@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 30453723 for ; Mon, 19 Aug 2013 07:00:02 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 1D9BA268C for ; Mon, 19 Aug 2013 07:00:02 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.7/8.14.7) with ESMTP id r7J701jU045666 for ; Mon, 19 Aug 2013 07:00:01 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.7/8.14.7/Submit) id r7J701I9045665; Mon, 19 Aug 2013 07:00:01 GMT (envelope-from gnats) Date: Mon, 19 Aug 2013 07:00:01 GMT Message-Id: <201308190700.r7J701I9045665@freefall.freebsd.org> To: freebsd-net@FreeBSD.org Cc: From: Julian Elischer Subject: Re: kern/181388: [route] Routes not updated on mtu change X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Julian Elischer List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Aug 2013 07:00:02 -0000 The following reply was made to PR kern/181388; it has been noted by GNATS. From: Julian Elischer To: bug-followup@FreeBSD.org, joe@rewt.org.uk Cc: Subject: Re: kern/181388: [route] Routes not updated on mtu change Date: Mon, 19 Aug 2013 14:57:22 +0800 The problem is that this is not as simple as it seems. The route MTU MIGHT have been set by something other than the interface MTU in the first place. The interface MTU is a default for the route MTU but is not the only source. This actuall bit me a couple of days ago when I was wonderign why my interface was not sending 9K packets.. turns out you need to do 'ifconfig_xn0="DHCP mtu 9000"' in order to have your dncp configured interface routes have the right size. so, I'm agreeing with you , but noticing that there are complications.