[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#533208: marked as done (IPv6 not working in OpenVZ containers with Lenny 2.6.26-openvz kernel)



Your message dated Sat, 27 Jun 2009 14:31:09 +0200
with message-id <20090627123109.GA2277@stro.at>
and subject line Re: Bug#533208: IPv6 not working in OpenVZ containers with Lenny 2.6.26-openvz kernel
has caused the Debian Bug report #533208,
regarding IPv6 not working in OpenVZ containers with Lenny 2.6.26-openvz kernel
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
533208: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=533208
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Package: linux-image-2.6.26-2-openvz-amd64
Version: 2.6.26-15lenny2
Tags: lenny,ipv6

IPv6 does not work in OpenVZ containers when hardware node is using the linux-image-2.6.26-2-openvz-amd64 kernel: containers are unable to reach any IPv6 host other than himself and the hardware node.

This does not affect the IPv6 connectivity of the hardware node itself, only hosted containers.

Booting the hardware node with the Debian-Systs 2.6.18 "Fortezza" kernel (linux-image-2.6.18-14-fza-amd64, version 028stab056.1dso1), without changing anything else, restores proper IPv6 functionlality in containers, so the issue seems kernel or kernel-version related.

This bug has been filed on the OpenVZ bug tracker:
http://bugzilla.openvz.org/show_bug.cgi?id=1287

Test setup is:
- Debian Lenny hardware node
- Debian Etch, Lenny and CentOS containers
- containers use venet devices
- IPv6 forwarding is globally enabled (/sbin/sysctl -q -w net.ipv6.conf.all.forwarding=1), and hardware node public ethernet device is statically IPv6-configured


--
Ce message a ete verifie par MailScanner
pour des virus ou des polluriels et rien de
suspect n'a ete trouve.




--- End Message ---
--- Begin Message ---
On Mon, 15 Jun 2009, Benoit Branciard wrote:

> the linux-image-2.6.26-2-openvz-amd64 kernel: containers are unable
> to reach any IPv6 host other than himself and the hardware node.
> 
> This does not affect the IPv6 connectivity of the hardware node
> itself, only hosted containers.
> 
> Booting the hardware node with the Debian-Systs 2.6.18 "Fortezza"
> kernel (linux-image-2.6.18-14-fza-amd64, version 028stab056.1dso1),
> without changing anything else, restores proper IPv6 functionlality
> in containers, so the issue seems kernel or kernel-version related.
> 
> This bug has been filed on the OpenVZ bug tracker:
> http://bugzilla.openvz.org/show_bug.cgi?id=1287
> 

thanks for having reported upstream, to enable ipv6 one has to:
echo 1 > /proc/sys/net/ipv6/conf/all/proxy_ndp

and for each VE :

echo ip -6 neigh add proxy $IPV6 dev eth0;


thus closing.


--- End Message ---

Reply to: