From owner-freebsd-hackers@FreeBSD.ORG Sat Feb 7 05:10:15 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 46CF12D4 for ; Sat, 7 Feb 2015 05:10:15 +0000 (UTC) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "gold.funkthat.com", Issuer "gold.funkthat.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 011BF697 for ; Sat, 7 Feb 2015 05:10:14 +0000 (UTC) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.14.5/8.14.5) with ESMTP id t175AD1q060287 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 6 Feb 2015 21:10:13 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.14.5/8.14.5/Submit) id t175ACJ0060286; Fri, 6 Feb 2015 21:10:12 -0800 (PST) (envelope-from jmg) Date: Fri, 6 Feb 2015 21:10:12 -0800 From: John-Mark Gurney To: "Pokala, Ravi" Subject: Re: Changing the MTU on a lagg device Message-ID: <20150207051012.GH58410@funkthat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD 9.1-PRERELEASE amd64 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.5.21 (2010-09-15) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.7 (gold.funkthat.com [127.0.0.1]); Fri, 06 Feb 2015 21:10:13 -0800 (PST) Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 07 Feb 2015 05:10:15 -0000 Ravi Pokala wrote this message on Sat, Feb 07, 2015 at 02:42 +0000: > Hi folks, > > Let's say you have lagg0, consisting of if0 and if1. If you want to change > the MTU, you have to remove if0 and if1 from the lagg, change their MTUs, > and add them back; that is: > > 1) ifconfig lagg0 -laggport if0 > 2) ifconfig lagg0 -laggport if1 > 3) ifconfig if0 mtu 9000 > 4) ifconfig if1 mtu 9000 > 5) ifconfig lagg0 laggport if0 > 6) ifconfig lagg0 laggport if1 > > It would be nice if this could be done with a single command: > > 1) ifconfig lagg0 mtu 9000 > > Panasas implemented that functionality for our older base FreeBSD, and > we're looking to port it forward and push it upstream. However, it looks > like someone thought about this case and explicitly decided not to do it; > if_lagg.c has: > > case SIOCSIFMTU: > /* Do not allow the MTU to be changed once joined */ > error = EINVAL; > break; > > > Does anyone know why that is? Would anyone object to a patch that lets you > change the MTU on the lagg device, and having the lagg driver change it on > all the component interfaces for you? If could be trying to deal w/ the issue if you ask for 16000 but one can do it, but the other can only handle 9000, how do you handle it? Just for fun, I just tried something similar.. lagg won't allow you to add a port that has a different (smaller or bigger) MTU than the first one added.. So, to do it, you'd need to try to change all the ports mtu, and if any of them fail, you need to revert all of them back to the original mtu... -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."