Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
Package: linux-2.6
Version: 2.6.32-18
Severity: important
Tags: squeeze
-- Package-specific info:
** Version:
Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-18) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:32:56 UTC 2010
** Network interface configuration:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The loopback network interface
auto lo
iface lo inet loopback
Kernel: Linux 2.6.32-5-openvz-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages linux-image-2.6.32-5-openvz-amd64 depends on:
ii debconf [debconf-2.0] 1.5.33 Debian configuration management sy
ii initramfs-tools [linux-initra 0.97.2 tools for generating an initramfs
ii linux-base 2.6.32-18 Linux image base package
ii module-init-tools 3.12-1 tools for managing Linux kernel mo
ii vzctl 3.0.23-18 server virtualization solution - c
Versions of packages linux-image-2.6.32-5-openvz-amd64 recommends:
pn firmware-linux-free <none> (no description available)
Versions of packages linux-image-2.6.32-5-openvz-amd64 suggests:
pn grub | lilo <none> (no description available)
pn linux-doc-2.6.32 <none> (no description available)
Versions of packages linux-image-2.6.32-5-openvz-amd64 is related to:
pn firmware-bnx2 <none> (no description available)
pn firmware-bnx2x <none> (no description available)
pn firmware-ipw2x00 <none> (no description available)
pn firmware-ivtv <none> (no description available)
pn firmware-iwlwifi <none> (no description available)
pn firmware-linux <none> (no description available)
pn firmware-linux-nonfree <none> (no description available)
pn firmware-qlogic <none> (no description available)
pn firmware-ralink <none> (no description available)
pn xen-hypervisor <none> (no description available)
- I have a VZ-Server based on Debian Squeeze AMD64 using the latest OpenVZ Kernel from Debian unstable 2.6.32-15. The system's other packages are up2date.
- The system has two ethernet-devices eth0 (external) and eth1, which is a phys. interface for a .1q-Trunk.
- I have two bridge-devices br0 and br1 with own IP-subnet and no attached phys. ethernet device to form "virtual dmz" on the host. The traffic is routed between the networks.
- There is a VE attached to every bridge device. It uses veth as network subsystem.
- I use Openswan 1:2.6.26+dfsg-1 for ipsec tunnels
The Problem:
I can access the VE from the LAN attached to e.g. eth0 or eth1.100 (VLAN) without any problem. I can also ping from one VE to the other or to hosts on the LAN.
I can use the VPN-Tunnel to ping hosts on the phys. LAN and I can also ping the host's IP-addresses on the bridge-device. But I _cannot_ ping the VE's IP itself using the ipsec tunnel. I can see the packages travelling to br1 in tcpdump, but the VE does not answer. I can also see the packages _inside_ the VE using tcpdump on eth0 but the VE does not answer.
The most strange thing is, if I ping back from the VE to the VPN-Client IP-Address I can see bidirectional traffic on br1 using tcpdump but the ping-command inside the VE does not get any packet back. The VPN-Client is 192.168.10.1 the VE has 172.16.231.129. This is what I see in tcpdump:
15:06:30.496483 IP 172.16.231.129 > 192.168.10.1: ICMP echo request, id 318, seq 10, length 64
15:06:30.498103 IP 192.168.10.1 > 172.16.231.129: ICMP echo reply, id 318, seq 10, length 64
15:06:31.504440 IP 172.16.231.129 > 192.168.10.1: ICMP echo request, id 318, seq 11, length 64
15:06:31.507335 IP 192.168.10.1 > 172.16.231.129: ICMP echo reply, id 318, seq 11, length 64
15:06:32.512414 IP 172.16.231.129 > 192.168.10.1: ICMP echo request, id 318, seq 12, length 64
15:06:32.532765 IP 192.168.10.1 > 172.16.231.129: ICMP echo reply, id 318, seq 12, length 64
15:06:33.520455 IP 172.16.231.129 > 192.168.10.1: ICMP echo request, id 318, seq 13, length 64
15:06:33.524663 IP 192.168.10.1 > 172.16.231.129: ICMP echo reply, id 318, seq 13, length 64
15:06:34.528431 IP 172.16.231.129 > 192.168.10.1: ICMP echo request, id 318, seq 14, length 64
15:06:34.530911 IP 192.168.10.1 > 172.16.231.129: ICMP echo reply, id 318, seq 14, length 64
And this what the ping shows if stopped after a while:
root@proxy:/# ip route list table all
172.16.231.128/25 dev eth0 proto kernel scope link src 172.16.231.129
default via 172.16.231.254 dev eth0
local 172.16.231.129 dev eth0 table local proto kernel scope host src 172.16.231.129
broadcast 172.16.231.128 dev eth0 table local proto kernel scope link src 172.16.231.129
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 172.16.231.255 dev eth0 table local proto kernel scope link src 172.16.231.129
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255
local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:febd:fe1d via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255
Routing-Table on the Host-System:
root@vzhost01:~# ip route list table all
213.178.168.248/29 dev eth1.100 proto kernel scope link src 213.178.168.253
212.9.191.0/25 dev eth0 proto kernel scope link src 212.9.191.121
172.16.231.128/25 dev br1 proto kernel scope link src 172.16.231.254
172.16.231.0/25 dev br0 proto kernel scope link src 172.16.231.126
default via 212.9.191.1 dev eth0
broadcast 212.9.191.127 dev eth0 table local proto kernel scope link src 212.9.191.121
broadcast 172.16.231.128 dev br1 table local proto kernel scope link src 172.16.231.254
broadcast 127.255.255.255 dev lo table local proto kernel scope link src 127.0.0.1
broadcast 213.178.168.248 dev eth1.100 table local proto kernel scope link src 213.178.168.253
broadcast 172.16.231.0 dev br0 table local proto kernel scope link src 172.16.231.126
broadcast 213.178.168.255 dev eth1.100 table local proto kernel scope link src 213.178.168.253
local 212.9.191.121 dev eth0 table local proto kernel scope host src 212.9.191.121
local 213.178.168.253 dev eth1.100 table local proto kernel scope host src 213.178.168.253
local 172.16.231.126 dev br0 table local proto kernel scope host src 172.16.231.126
broadcast 172.16.231.127 dev br0 table local proto kernel scope link src 172.16.231.126
local 172.16.231.254 dev br1 table local proto kernel scope host src 172.16.231.254
broadcast 212.9.191.0 dev eth0 table local proto kernel scope link src 212.9.191.121
broadcast 172.16.231.255 dev br1 table local proto kernel scope link src 172.16.231.254
broadcast 127.0.0.0 dev lo table local proto kernel scope link src 127.0.0.1
local 127.0.0.1 dev lo table local proto kernel scope host src 127.0.0.1
local 127.0.0.0/8 dev lo table local proto kernel scope host src 127.0.0.1
fe80::/64 dev eth1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth1.100 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev br1 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev br0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev veth100.0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev veth200.0 proto kernel metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255
local ::1 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:fe7f:1f38 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::218:51ff:fe86:1506 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::5054:ff:fe91:f85d via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::5054:ff:fe91:f85d via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::5054:ff:fedd:5e72 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::ac33:a8ff:fe5b:a9e9 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
local fe80::cc5e:d0ff:fe76:5956 via :: dev lo table local proto none metric 0 mtu 16436 advmss 16376 hoplimit 4294967295
ff00::/8 dev eth1 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth1.100 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev br1 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev br0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev eth0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev veth100.0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
ff00::/8 dev veth200.0 table local metric 256 mtu 1500 advmss 1440 hoplimit 4294967295
unreachable default dev lo table unspec proto kernel metric -1 error -101 hoplimit 255
I am sure, that there are no iptables-filters active. Here comes the dump:
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100728082940.32051.68705.reportbug@osfw-v3-01.LF.net">http://lists.debian.org/20100728082940.32051.68705.reportbug@osfw-v3-01.LF.net
07-28-2010, 08:50 AM
maximilian attems
Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
On Wed, Jul 28, 2010 at 10:29:40AM +0200, Daniel Tombeil wrote:
> Package: linux-2.6
> Version: 2.6.32-18
> Severity: important
> Tags: squeeze
>
>
>
> -- Package-specific info:
> ** Version:
> Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-18) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:32:56 UTC 2010
>
> ** Command line:
> BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-openvz-amd64 root=/dev/mapper/osfw--v3--01--vda1-osfw--v3--01--root ro quiet
see no posted evidence here, but anyway please post tcpdumps
and setup in upstream bugzilla.openvz.org and let us know bug nr
so that it can be tracked.
thanks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100728085026.GL19138@baikonur.stro.at">http://lists.debian.org/20100728085026.GL19138@baikonur.stro.at
07-28-2010, 09:09 AM
Daniel Tombeil
Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
Hi,
On Wed, 2010-07-28 at 10:50 +0200, maximilian attems wrote:
> On Wed, Jul 28, 2010 at 10:29:40AM +0200, Daniel Tombeil wrote:
> > Package: linux-2.6
> > Version: 2.6.32-18
> > Severity: important
> > Tags: squeeze
> >
> >
> >
> > -- Package-specific info:
> > ** Version:
> > Linux version 2.6.32-5-openvz-amd64 (Debian 2.6.32-18) (ben@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Sat Jul 24 02:32:56 UTC 2010
> >
> > ** Command line:
> > BOOT_IMAGE=/boot/vmlinuz-2.6.32-5-openvz-amd64 root=/dev/mapper/osfw--v3--01--vda1-osfw--v3--01--root ro quiet
>
> see no posted evidence here, but anyway please post tcpdumps
> and setup in upstream bugzilla.openvz.org and let us know bug nr
> so that it can be tracked.
I attached some ASCII-tcpdump output at the end of the report. Below the
"More information:"-Line.
But I'll try if it is reproducable in an easier setup. base-install, one
bridge-device, and then trying to access the veth-attached VE's on the
bridge-devices network using an ipsec tunnel terminated using openswan
in netkey-mode. I'll post the setup-guide for reproduction and the
binary tcpdump ASAP.
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 1280308181.27040.11.camel@tomte.LF.net">http://lists.debian.org/1280308181.27040.11.camel@tomte.LF.net
07-28-2010, 09:30 AM
maximilian attems
Bug#590661: linux-image-2.6.32-5-openvz-amd64: openswan ipsec packets do not reach openvz instances
On Wed, Jul 28, 2010 at 11:09:41AM +0200, Daniel Tombeil wrote:
>
> > see no posted evidence here, but anyway please post tcpdumps
> > and setup in upstream bugzilla.openvz.org and let us know bug nr
> > so that it can be tracked.
>
> I attached some ASCII-tcpdump output at the end of the report. Below the
> "More information:"-Line.
>
> But I'll try if it is reproducable in an easier setup. base-install, one
> bridge-device, and then trying to access the veth-attached VE's on the
> bridge-devices network using an ipsec tunnel terminated using openswan
> in netkey-mode. I'll post the setup-guide for reproduction and the
> binary tcpdump ASAP.
ok sorry overlooked, as wasn't in body, please make upstream devs
aware by filing there.
development and fixes happens there. thanks
--
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100728093050.GM19138@baikonur.stro.at">http://lists.debian.org/20100728093050.GM19138@baikonur.stro.at