From: David Miller Subject: Re: [PATCH] veth: Allow setting the L3 MTU Date: Tue, 03 Mar 2009 23:36:16 -0800 (PST) Message-ID: <20090303.233616.17571375.davem@davemloft.net> References: Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Sender: netdev-owner@vger.kernel.org To: ebiederm@xmission.com Cc: netdev@vger.kernel.org, containers@lists.osdl.org, dlezcano@fr.ibm.com, xemul@openvz.org List-Id: containers.vger.kernel.org From: ebiederm@xmission.com (Eric W. Biederman) Date: Tue, 03 Mar 2009 20:14:18 -0800 > The limitation to only 1500 byte mtu's limits the utility of the veth > device for testing routing. So implement implement a configurable > MTU. > > For consistency I drop packets on the receive side when they are > larger than the MTU. I count those drops. And I allow > a little padding for vlan headers. > > I also test the mtu when a new device is created with netlink > because that path currently bypasses the current mtu setting > code. > > Signed-off-by: Eric Biederman Applied to net-next-2.6, thanks Eric.