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: <1b4cfd95-4242-c0a6-7cd4-43fa037e2bae@secunet.com>
Date:	Thu, 4 Aug 2016 08:20:24 +0200
From:	Alexander Heinlein <alexander.heinlein@...unet.com>
To:	<netdev@...r.kernel.org>
CC:	<nicolas.dichtel@...nd.com>
Subject: IPIP tunnel with fixed TTL but no DF bit

Hi,

I would like to know why ip_tunnel_ioctl() enforces the DF bit whenever
the tunnel device has a fixed TTL set. The same restriction is enforced
by iproute2 (iptunnel.c and link_iptnl.c).

Ideally I would like to use an IPIP tunnel with a fixed TTL but no DF
bit set. Otherwise for non-TCP packets that are larger than the PMTU
size the kernel will send ICMP packets to end systems. However these
ICMP packets are ignored by the end system since the original packets
didn't have the DF bit set. As a result, non-TCP packets larger than the
PMTU are being dropped.

Regards
Alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ