netdev - Re: [PATCH] Configurable tap interface 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <e6c711510709120954i29a8f86bg9ea7bb337a039b5a@mail.gmail.com>
Date:	Wed, 12 Sep 2007 09:54:35 -0700
From:	"Ed Swierk" <eswierk@...stra.com>
To:	"Herbert Xu" <herbert@...dor.apana.org.au>, netdev@...r.kernel.org,
	maxk@...lcomm.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Configurable tap interface MTU

On 9/11/07, Herbert Xu <herbert@...dor.apana.org.au> wrote:
> Please make it 65535 without an Ethernet header and 65521
> with an Ethernet header.

Here is a revised patch that allows MTUs up to 65535 for tap
interfaces and up to 65521 for tun interfaces.

(If I set the MTU to 65521 on a tun interface, ping complains "message
too long" when I send a 65521-byte packet; 65520 works okay, though.)

--Ed

Download attachment "tap-change-mtu.patch" of type "application/octet-stream" (1185 bytes)