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: <EB8510AA7A943D43916A72C9B8F4181F629D9741@cvk038.intra.cvk.de>
Date:   Fri, 13 Sep 2019 08:59:00 +0000
From:   "Bartschies, Thomas" <Thomas.Bartschies@....de>
To:     "'netdev@...r.kernel.org'" <netdev@...r.kernel.org>
Subject: big ICMP requests get disrupted on IPSec tunnel activation

Hello together,

since kenel 4.20 we're observing a strange behaviour when sending big ICMP packets. An example is a packet size of 3000 bytes.
The packets should be forwarded by a linux gateway (firewall) having multiple interfaces also acting as a vpn gateway.

Test steps:
1. Disabled all iptables rules
2. Enabled the VPN IPSec Policies.
3. Start a ping with packet size (e.g. 3000 bytes) from a client in the DMZ passing the machine targeting another LAN machine
4. Ping works
5. Enable a VPN policy by sending pings from the gateway to a tunnel target. System tries to create the tunnel
6. Ping from 3. immediately stalls. No error messages. Just stops.
7. Stop Ping from 3. Start another without packet size parameter. Stalls also.

Result:
Connections from the client to other services on the LAN machine still work. Tracepath works. Only ICMP requests do not pass
the gateway anymore. tcpdump sees them on incoming interface, but not on the outgoing LAN interface. IMCP requests to any
other target IP address in LAN still work. Until one uses a bigger packet size. Then these alternative connections stall also.

Flushing the policy table has no effect. Flushing the conntrack table has no effect. Setting rp_filter to loose (2) has no effect.
Flush the route cache has no effect.

Only a reboot of the gateway restores normal behavior.

What can be the cause? Is this a networking bug?

Best regards,
--
i. A. Thomas Bartschies 
IT Systeme

Cornelsen Verlagskontor GmbH
Kammerratsheide 66
33609 Bielefeld
Telefon: +49 (0)521 9719-310
Telefax: +49 (0)521 9719-93310
thomas.bartschies@....de
http://www.cvk.de
AG Bielefeld HRB 39324
Geschäftsführer: Thomas Fuchs, Patrick Neiss



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ