netdev - Re: [PATCH] veth: Allow setting the L3 MTU

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 03 Mar 2009 23:36:16 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	ebiederm@...ssion.com
Cc:	netdev@...r.kernel.org, containers@...ts.osdl.org,
	dlezcano@...ibm.com, xemul@...nvz.org
Subject: Re: [PATCH] veth: Allow setting the L3 MTU

From: ebiederm@...ssion.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 <ebiederm@...stanetworks.com>

Applied to net-next-2.6, thanks Eric.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html