Text only | Text with Images

Hurricane Electric's IPv6 Tunnel Broker Forums

General IPv6 Topics => IPv6 on Linux & BSD & Mac => Topic started by: vpsnoc on January 30, 2010, 01:05:44 AM

Title: IPv6 on openvz container
Post by: vpsnoc on January 30, 2010, 01:05:44 AM
Hello, I followed the instructions posted here http://www.tunnelbroker.net/forums/index.php?topic=152.0 to setup a tunnel on the hardware node.
IPv6 works just fine on the hardware node, this is my output from ifconfig
Code Select

eth0      Link encap:Ethernet  HWaddr 00:01:6C:65:53:A9
          inet addr:69.197.xxx.xxx  Bcast:69.197.xxx.1xx  Mask:255.255.255.240
          inet6 addr: fe80::201:6cff:fe65:53a9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:30651559 errors:0 dropped:0 overruns:0 frame:0
          TX packets:33385450 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:16341397515 (15.2 GiB)  TX bytes:22785688012 (21.2 GiB)
          Interrupt:50 Base address:0xe000

he-ipv6   Link encap:IPv6-in-IPv4
          inet6 addr: 2001:470:1f10:450::2/64 Scope:Global
          inet6 addr: fe80::45c5:9892/128 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:11 errors:0 dropped:0 overruns:0 frame:0
          TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1120 (1.0 KiB)  TX bytes:720 (720.0 b)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:12 errors:0 dropped:0 overruns:0 frame:0
          TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:600 (600.0 b)  TX bytes:600 (600.0 b)

sit0      Link encap:IPv6-in-IPv4
          inet6 addr: ::69.197.xxx.xxx/96 Scope:Compat
          inet6 addr: ::127.0.0.1/96 Scope:Unknown
          UP RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

sit1      Link encap:IPv6-in-IPv4
          inet6 addr: 2001:470:1f10:450::2/64 Scope:Global
          inet6 addr: fe80::45c5:9892/64 Scope:Link
          UP POINTOPOINT RUNNING NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:73 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:7420 (7.2 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:32713884 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29796853 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:22249542602 (20.7 GiB)  TX bytes:15647893530 (14.5 GiB)'

So I assigned the ::3 IP address from my subnet on an openvz container and I can't even ping the ::2 IP address on the hardware node let alone anything from outside
Code Select

root@vpn:/# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:46 errors:0 dropped:0 overruns:0 frame:0
          TX packets:46 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:3056 (3.0 KB)  TX bytes:3056 (3.0 KB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: ::1/128 Scope:Host
          inet6 addr: 2001:470:1f10:450::3/128 Scope:Global
          inet6 addr: 2001:470:1f10:450::5/128 Scope:Global
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:25797 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29640 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2518329 (2.5 MB)  TX bytes:4812570 (4.8 MB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:69.197.xxx.xxx  P-t-P:69.197.xxx.xxx  Bcast:0.0.0.0  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
root@vpn:/# ping6 2001:470:1f10:450::2
connect: Network is unreachable
root@vpn:/# ping6 2001:470:1f10:450::1
connect: Network is unreachable
root@vpn:/# ping6 ipv6.google.com
connect: Network is unreachable
root@vpn:/#

Can someone please shed a light on this? /proc/sys/net/ipv6/conf/all/forwarding is set to 1
What have I've done wrong?

Thank you.
Title: Re: IPv6 on openvz container
Post by: broquea on January 30, 2010, 01:17:13 AM
Try using the routed /64 first of all on your VE's, like my thread stated. Also might be some ip6tables issues either inside the VE or the HN. I run with iptables/ip6tables completely disabled as I have no need for them. Also what is your ipv6 routing table looking like in the VE? might need to tell it where to find default if it doesn't know. Also, what distro are you using inside the VE?
Title: Re: IPv6 on openvz container
Post by: vpsnoc on January 30, 2010, 01:37:22 AM
Ah I figured it out. the ::/0 route was on the lo interface rather than the venet0
Code Select

route -A inet6 add ::/0 dev venet0

Fixed it for future reference.

Thank you for pointing out the routing broquea.
Text only | Text with Images