From owner-freebsd-net@freebsd.org Thu Jul 16 14:53:16 2015 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id EFBA59A1CAD for ; Thu, 16 Jul 2015 14:53:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from mail.tdx.com (mail.tdx.com [62.13.128.18]) by mx1.freebsd.org (Postfix) with ESMTP id BEB661C3D for ; Thu, 16 Jul 2015 14:53:16 +0000 (UTC) (envelope-from kpielorz_lst@tdx.co.uk) Received: from [10.12.30.106] (vpn01-01.tdx.co.uk [62.13.130.213]) (authenticated bits=0) by mail.tdx.com (8.14.3/8.14.3/) with ESMTP id t6GEr8Nr042377 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Jul 2015 15:53:09 +0100 (BST) Date: Thu, 16 Jul 2015 15:53:08 +0100 From: Karl Pielorz To: John-Mark Gurney cc: freebsd-net@freebsd.org Subject: Re: lagg of em0/em1 + VLAN = lower MTU? Message-ID: <162CD3DC2BDDC847DF7987D0@[10.12.30.106]> In-Reply-To: <20150713165631.GN8523@funkthat.com> References: <7CFE75F7566F5789DAD9FBB2@[10.12.30.106]> <20150710180627.GA8523@funkthat.com> <20150713165631.GN8523@funkthat.com> X-Mailer: Mulberry/4.0.8 (Win32) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 16 Jul 2015 14:53:17 -0000 --On 13 July 2015 09:56 -0700 John-Mark Gurney wrote: > You can fix the untagged traffic on lagg0 with something like the > following: > route change -mtu 1500 > > You can see which routes need to be changed w/ the netstat -rWnfinet > command... Ok, that works. It's clunky - but it works... > You should be able to make it work, but it definately needs more work > to make it work automaticly... There was a recent change that went > in that makes changing lagg mtu easier, but I think that's only in > HEAD right now... Presumably, other people configuring it don't run into the issue (lagg+VLAN) because of different FreeBSD version / NIC's? Is the issue just that the VLAN code thinks the LAGG is the parent, and doesn't "see" the underlying card is long-frame capable? Or is it as simple as the em cards not being listed as 'long-frame capable' (i.e. from the man page). > Hope this helps... Certainly appears to have, thanks! -Karl