| 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
| ||
|
Date: Wed, 6 Jan 2016 13:33:04 +0000 From: David Wragg <david@...ve.works> To: netdev@...r.kernel.org, dev@...nvswitch.org Cc: David Wragg <david@...ve.works> Subject: [PATCH net 0/2] vxlan: Set a large MTU on ovs-created vxlan devices Prior to 4.3, openvswitch vxlan vports could transmit vxlan packets of any size, constrained only by the ability to transmit the resulting UDP packets. 4.3 introduced vxlan netdevs corresponding to vxlan vports. These netdevs have an MTU, which limits the size of a packet that can be successfully vxlan-encapsulated. The default value for this MTU is 1500, which is awkwardly small, and leads to a conspicuous change in behaviour for userspace. These two patches set the MTU on openvswitch-crated vxlan devices to be 65465 (the maximum IP packet size minus the vxlan-on-IPv6 overhead), effectively restoring the behaviour prior to 4.3. In order to accomplish this, the first patch removes the MTU constraint of 1500 for vxlan netdevs without an underlying device. David Wragg (2): vxlan: Relax the MTU constraint on vxlan devices vxlan: Set a large MTU on ovs-created vxlan devices drivers/net/vxlan.c | 38 +++++++++++++++++++++++++------------- net/openvswitch/vport-vxlan.c | 2 ++ 2 files changed, 27 insertions(+), 13 deletions(-) -- 2.5.0 -- 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
Powered by blists - more mailing lists