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
| ||
|
Message-ID: <000301cac9a8$dcd53750$967fa5f0$@no> Date: Mon, 22 Mar 2010 11:17:17 +0100 From: "Kristian Evensen" <kristrev@...ula.no> To: <netdev@...r.kernel.org>, <linux-ppp@...r.kernel.org> Subject: Performance hit with IP-tunnels Hello, I am currently comparing different IP-tunneling protocols/implementations, and have stumbled upon something I am not able to explain. Regardless of which tunneling technology I use, the latency increases with a couple of 10s of ms and I see a significant degradation of throughput (compared to when no tunnels are used). The only exception is IP-in-IP, where I get similar performance with and without tunnels, but it does unfortunately not work in my scenario. First, I thought this was caused by the different tunneling software, but after measuring the processing time of the applications (xl2tp and pptp-client) and when the packets are seen by the different iptables chains (using LOG), these delays seem to be acceptable. However, one delay sticks out. After the packet has been decapsulated and fed to PPP, it takes a "long" time before it is seen again. My question is, can PPP be the cause of the higher latency and lower throughput? Similar observations are made at both ends of the tunnel. Thanks in advance for any help, Kristian -- 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