Re: [PATCH] Configurable tap interface MTU

2007-09-16 Thread David Miller
From: "Ed Swierk" <[EMAIL PROTECTED]> Date: Wed, 12 Sep 2007 09:54:35 -0700 > On 9/11/07, Herbert Xu <[EMAIL PROTECTED]> 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

Re: [PATCH] Configurable tap interface MTU

2007-09-12 Thread Ed Swierk
On 9/11/07, Herbert Xu <[EMAIL PROTECTED]> 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

Re: [PATCH] Configurable tap interface MTU

2007-09-11 Thread Herbert Xu
Ed Swierk <[EMAIL PROTECTED]> wrote: > > The patch caps the MTU somewhat arbitrarily at 16000 bytes. This is > slightly lower than the value used by the e1000 driver, so it seems > like a safe upper limit. Please make it 65535 without an Ethernet header and 65521 with an Ethernet header. Cheers,

Re: [PATCH] Configurable tap interface MTU

2007-09-11 Thread Rick Jones
Ed Swierk wrote: This patch makes it possible to change the MTU on a tap interface. Increasing the MTU beyond the 1500-byte default is useful for applications that interoperate with Ethernet devices supporting jumbo frames. The patch caps the MTU somewhat arbitrarily at 16000 bytes. This is slig

[PATCH] Configurable tap interface MTU

2007-09-11 Thread Ed Swierk
This patch makes it possible to change the MTU on a tap interface. Increasing the MTU beyond the 1500-byte default is useful for applications that interoperate with Ethernet devices supporting jumbo frames. The patch caps the MTU somewhat arbitrarily at 16000 bytes. This is slightly lower than the