linux-kernel - Per route MTU settings are broken in linux kernel 3.2

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-next>] [day] [month] [year] [list]

Message-ID: <1372063443.32157.10.camel@linux>
Date:	Mon, 24 Jun 2013 15:44:03 +0700
From:	Yura Pakhuchiy <pakhuchiy@...il.com>
To:	Ben Hutchings <ben@...adent.org.uk>
Cc:	linux-kernel@...r.kernel.org
Subject: Per route MTU settings are broken in linux kernel 3.2

Hello Ben,

Looks like setting per route MTU (as described in [1]) is broken in
Linux kernel 3.2. I tested with newer Ubuntu kernels 3.5 and 3.8 and it
looks like problem is fixed there. I filled Ubuntu bug report [2] with
more details and sample script which illustrates problem. But since this
problem is probably also present in stock kernel (not just in Ubuntu),
is it possible to backport fixes to stable 3.2 series?

1. http://lartc.org/howto/lartc.cookbook.mtu-discovery.html
2. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1177507

-- 
Best regards,
        Yura

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/