netdev - Re: [RFC PATCH] veth: keep peers MTU values synchronized

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]

Date:	Fri, 04 Apr 2014 10:25:18 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	matvejchikov@...il.com
Cc:	netdev@...r.kernel.org, i.matveychikov@...uritycode.ru
Subject: Re: [RFC PATCH] veth: keep peers MTU values synchronized

From: "Ilya V. Matveychikov" <matvejchikov@...il.com>
Date: Fri, 04 Apr 2014 01:33:04 +0400

> Keep peers MTU values synchronized. That prevent dropping packets
> while
> forwarding as diffirent MTU values prevent skb moving from one peer's
> device to another (is_skb_forwardable returns false).
> 
> Signed-off-by: Ilya V. Matveychikov <i.matveychikov@...uritycode.ru>

Such side effects on another device when changing the configuration
of one are strongly discouraged.

Furthermore, when the veth peer is created, no attempt is made to
synchronize the MTUs.

Let it therefore be the admins responsibility to keep them in sync
just as it would be on a real network.
--
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