From owner-freebsd-net@FreeBSD.ORG Mon Aug 19 08:32:22 2013 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id EE6EE6FF for ; Mon, 19 Aug 2013 08:32:22 +0000 (UTC) (envelope-from lists@rewt.org.uk) Received: from hosted.mx.as41113.net (abby.lhr1.as41113.net [91.208.177.20]) by mx1.freebsd.org (Postfix) with ESMTP id B63E82AE6 for ; Mon, 19 Aug 2013 08:32:21 +0000 (UTC) Received: from [192.168.1.54] (staff-ns50-3.as25178.net [212.9.98.1]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: lists@rewt.org.uk) by hosted.mx.as41113.net (Postfix) with ESMTPSA id 3cJT041rDyzN7 for ; Mon, 19 Aug 2013 09:32:20 +0100 (BST) Message-ID: <5211D812.5070308@rewt.org.uk> Date: Mon, 19 Aug 2013 09:32:18 +0100 From: Joe Holden User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 MIME-Version: 1.0 To: freebsd-net@freebsd.org Subject: Re: kern/181388: [route] Routes not updated on mtu change References: <201308190700.r7J701I9045665@freefall.freebsd.org> In-Reply-To: <201308190700.r7J701I9045665@freefall.freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list 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 08:32:23 -0000 Hm, I hadn't considered that... how do other OSes and vendors handle this? (eg Linux?) Just changing the connected route would probably suffice, or maybe if any routes not added with default interface mtu could/are be flagged, then those could be changed or not depending on what added them? Perhaps need someone with more experience of the network stack to wade in here... Cheers, Joe On 19/08/2013 08:00, Julian Elischer wrote: > 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. > > > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >