[Users] IPv6 Non-Functional - 3.10.0-1160.80.1.vz7.191.4
Hello, Ever since updating to 3.10.0-1160.80.1.vz7.191.4, I've found that IPv6 no longer works, on both the host node and VPS' on it: [root@test ~]# ping6 google.com PING google.com(ams17s10-in-x0e.1e100.net (2a00:1450:400e:801::200e)) 56 data bytes ^C --- google.com ping statistics --- 83 packets transmitted, 0 received, 100% packet loss, time 82000ms [root@test ~]# The only "fix" I know of is to restart networking on the host node - which isn't ideal as it knocks out networking on VPS', and only provides temporary relief anyway. I'm aware from industry forums that this problem is not unique to me. I've tried AlmaLinux, Debian, Ubuntu, etc - it happens with all Linux distributions - clean install or not. Just curious - outside out restarting networking, or downgrading the kernel, does anyone know of a fix for this issue? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
Yes, br0 contains main server`s IPv4. So I perform tuning and now my IPv6 address pingable - but from this node only (and not on CTs on this node). This node CTs or other internet places - they do not see my IPv6. Other 2 secondary IPv6 addresses not even pingable from node. My steps: # nano -w /etc/sysconfig/network-scripts/ifcfg-br0 IPV6INIT=yes IPV6_AUTOCONF=no IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6ADDR=myIPv6IP_1 IPV6ADDR_SECONDARIES=myIPv6IP_2 myIPv6IP_3 IPV6_DEFAULTGW=myIPv6GW # nano -w /etc/sysconfig/network NETWORKING_IPV6=yes IPV6FORWARDING=yes IPV6_DEFAULTDEV=br0 IPV6_DEFAULTGW=myIPv6GW IPV6_AUTOCONF=no # echo "net.ipv6.conf.default.forwarding = 1" >> /etc/sysctl.conf # echo "net.ipv6.conf.all.forwarding = 1" >> /etc/sysctl.conf # echo "net.ipv6.conf.all.proxy_ndp = 1" >> /etc/sysctl.conf # sysctl -p # nano -w /etc/sysconfig/iptables-config IP6TABLES_MODULES="ip6_tables ip6table_filter ip6table_mangle ip6t_REJECT nf_conntrack_ipv6" # reboot -n чт, 15 груд. 2022 р. о 14:34 Arjit Chaudhary пише: > Hi, > It could be in br0 if you are bridging enp3s0f0 and/or enp3s0f1 > > Basically the interface which lists as UP and with the IPv4 information > etc should be the right one in my experience. > > But do back-up original configuration files on the system, before editing > just incase something goes wrong you can just copy them back and restart > networking. > > > On Thu, 15 Dec, 2022, 17:40 Oleksiy Tkachenko, wrote: > >> I have many) >> # ip a >> 1: lo: >> 2: enp3s0f0: >> 3: enp3s0f1: >> 4: enp0s20f0u9u2c2: >> 5: br0: >> 6: virbr0: >> 7: virbr0-nic: >> 8: venet0: >> 9: host-routed: >> 11: veth72240bcc@if3: >> 12: veth720bed05@if3: >> 13: veth7290a381@if3: >> 16: veth721813e6@if3: >> 17: veth720a338a@if3: >> 24: veth729a3460@if3: >> 25: veth720c6518@if3: >> 26: veth721bbb55@if3: >> 27: veth72705632@if3: >> 28: veth72b28dcd@if3: >> >> >> чт, 15 груд. 2022 р. о 13:52 Arjit Chaudhary пише: >> >>> Is your interface name different by chance? >>> >>> Can you check, >>> >>> > ip a >>> >>> for the actual interface name and then update that interface >>> configuration for the IPv6. >>> >>> On Thu, 15 Dec, 2022, 16:43 Oleksiy Tkachenko, >>> wrote: >>> Thank you! During node preparation I need to update "/etc/sysconfig/network-scripts/ifcfg-ethX" - but there is no such file. I also need to put "eth0" in "/etc/sysconfig/network" file - is it actual now (when I have no ethX file)? I also need to "Add 'ipt_state' to IPTABLES and 'nf_conntrack_ipv6' to IP6TABLES" in "/etc/vz.conf" - there is no such file also. I have "/etc/vz/vz.conf" on my bare metal openvz7 but there is no "IPTABLES" or "IP6TABLES" mention at all. чт, 15 груд. 2022 р. о 02:03 Arjit Chaudhary пише: > (In my experience) > > Does the host-node have working IPv6 configured on it? If yes, > > Then you can just do, > > vzctl set --ipadd -- save > > and the container too will have working IPv6. > > If the host-node does not have working IPv6, then you can just > configure any address of the IPv6 range on the host-node > > > On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: > >> Trying to setup IPv6 for CentOS7 CT. >> Seems original documentation outdated a bit ( >> https://wiki.openvz.org/IPv6). >> Is there updated information? >> >> Thank you! >> >> >> -- >> Oleksiy >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > > > -- > Thanks, > Arjit Chaudhary > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users >>> ___ >>> Users mailing list >>> Users@openvz.org >>> https://lists.openvz.org/mailman/listinfo/users >>> >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
Hi, It could be in br0 if you are bridging enp3s0f0 and/or enp3s0f1 Basically the interface which lists as UP and with the IPv4 information etc should be the right one in my experience. But do back-up original configuration files on the system, before editing just incase something goes wrong you can just copy them back and restart networking. On Thu, 15 Dec, 2022, 17:40 Oleksiy Tkachenko, wrote: > I have many) > # ip a > 1: lo: > 2: enp3s0f0: > 3: enp3s0f1: > 4: enp0s20f0u9u2c2: > 5: br0: > 6: virbr0: > 7: virbr0-nic: > 8: venet0: > 9: host-routed: > 11: veth72240bcc@if3: > 12: veth720bed05@if3: > 13: veth7290a381@if3: > 16: veth721813e6@if3: > 17: veth720a338a@if3: > 24: veth729a3460@if3: > 25: veth720c6518@if3: > 26: veth721bbb55@if3: > 27: veth72705632@if3: > 28: veth72b28dcd@if3: > > > чт, 15 груд. 2022 р. о 13:52 Arjit Chaudhary пише: > >> Is your interface name different by chance? >> >> Can you check, >> >> > ip a >> >> for the actual interface name and then update that interface >> configuration for the IPv6. >> >> On Thu, 15 Dec, 2022, 16:43 Oleksiy Tkachenko, >> wrote: >> >>> Thank you! >>> During node preparation I need to update >>> "/etc/sysconfig/network-scripts/ifcfg-ethX" - but there is no such file. >>> I also need to put "eth0" in "/etc/sysconfig/network" file - is it >>> actual now (when I have no ethX file)? >>> >>> I also need to "Add 'ipt_state' to IPTABLES and 'nf_conntrack_ipv6' to >>> IP6TABLES" in "/etc/vz.conf" - there is no such file also. >>> I have "/etc/vz/vz.conf" on my bare metal openvz7 but there is no >>> "IPTABLES" or "IP6TABLES" mention at all. >>> >>> >>> чт, 15 груд. 2022 р. о 02:03 Arjit Chaudhary пише: >>> (In my experience) Does the host-node have working IPv6 configured on it? If yes, Then you can just do, vzctl set --ipadd -- save and the container too will have working IPv6. If the host-node does not have working IPv6, then you can just configure any address of the IPv6 range on the host-node On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: > Trying to setup IPv6 for CentOS7 CT. > Seems original documentation outdated a bit ( > https://wiki.openvz.org/IPv6). > Is there updated information? > > Thank you! > > > -- > Oleksiy > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > -- Thanks, Arjit Chaudhary ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users >>> ___ >>> Users mailing list >>> Users@openvz.org >>> https://lists.openvz.org/mailman/listinfo/users >>> >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
I have many) # ip a 1: lo: 2: enp3s0f0: 3: enp3s0f1: 4: enp0s20f0u9u2c2: 5: br0: 6: virbr0: 7: virbr0-nic: 8: venet0: 9: host-routed: 11: veth72240bcc@if3: 12: veth720bed05@if3: 13: veth7290a381@if3: 16: veth721813e6@if3: 17: veth720a338a@if3: 24: veth729a3460@if3: 25: veth720c6518@if3: 26: veth721bbb55@if3: 27: veth72705632@if3: 28: veth72b28dcd@if3: чт, 15 груд. 2022 р. о 13:52 Arjit Chaudhary пише: > Is your interface name different by chance? > > Can you check, > > > ip a > > for the actual interface name and then update that interface configuration > for the IPv6. > > On Thu, 15 Dec, 2022, 16:43 Oleksiy Tkachenko, wrote: > >> Thank you! >> During node preparation I need to update >> "/etc/sysconfig/network-scripts/ifcfg-ethX" - but there is no such file. >> I also need to put "eth0" in "/etc/sysconfig/network" file - is it actual >> now (when I have no ethX file)? >> >> I also need to "Add 'ipt_state' to IPTABLES and 'nf_conntrack_ipv6' to >> IP6TABLES" in "/etc/vz.conf" - there is no such file also. >> I have "/etc/vz/vz.conf" on my bare metal openvz7 but there is no >> "IPTABLES" or "IP6TABLES" mention at all. >> >> >> чт, 15 груд. 2022 р. о 02:03 Arjit Chaudhary пише: >> >>> (In my experience) >>> >>> Does the host-node have working IPv6 configured on it? If yes, >>> >>> Then you can just do, >>> >>> vzctl set --ipadd -- save >>> >>> and the container too will have working IPv6. >>> >>> If the host-node does not have working IPv6, then you can just configure >>> any address of the IPv6 range on the host-node >>> >>> >>> On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: >>> Trying to setup IPv6 for CentOS7 CT. Seems original documentation outdated a bit ( https://wiki.openvz.org/IPv6). Is there updated information? Thank you! -- Oleksiy ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users >>> >>> >>> -- >>> Thanks, >>> Arjit Chaudhary >>> ___ >>> Users mailing list >>> Users@openvz.org >>> https://lists.openvz.org/mailman/listinfo/users >>> >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
Is your interface name different by chance? Can you check, > ip a for the actual interface name and then update that interface configuration for the IPv6. On Thu, 15 Dec, 2022, 16:43 Oleksiy Tkachenko, wrote: > Thank you! > During node preparation I need to update > "/etc/sysconfig/network-scripts/ifcfg-ethX" - but there is no such file. > I also need to put "eth0" in "/etc/sysconfig/network" file - is it actual > now (when I have no ethX file)? > > I also need to "Add 'ipt_state' to IPTABLES and 'nf_conntrack_ipv6' to > IP6TABLES" in "/etc/vz.conf" - there is no such file also. > I have "/etc/vz/vz.conf" on my bare metal openvz7 but there is no > "IPTABLES" or "IP6TABLES" mention at all. > > > чт, 15 груд. 2022 р. о 02:03 Arjit Chaudhary пише: > >> (In my experience) >> >> Does the host-node have working IPv6 configured on it? If yes, >> >> Then you can just do, >> >> vzctl set --ipadd -- save >> >> and the container too will have working IPv6. >> >> If the host-node does not have working IPv6, then you can just configure >> any address of the IPv6 range on the host-node >> >> >> On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: >> >>> Trying to setup IPv6 for CentOS7 CT. >>> Seems original documentation outdated a bit ( >>> https://wiki.openvz.org/IPv6). >>> Is there updated information? >>> >>> Thank you! >>> >>> >>> -- >>> Oleksiy >>> ___ >>> Users mailing list >>> Users@openvz.org >>> https://lists.openvz.org/mailman/listinfo/users >>> >> >> >> -- >> Thanks, >> Arjit Chaudhary >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
Thank you! During node preparation I need to update "/etc/sysconfig/network-scripts/ifcfg-ethX" - but there is no such file. I also need to put "eth0" in "/etc/sysconfig/network" file - is it actual now (when I have no ethX file)? I also need to "Add 'ipt_state' to IPTABLES and 'nf_conntrack_ipv6' to IP6TABLES" in "/etc/vz.conf" - there is no such file also. I have "/etc/vz/vz.conf" on my bare metal openvz7 but there is no "IPTABLES" or "IP6TABLES" mention at all. чт, 15 груд. 2022 р. о 02:03 Arjit Chaudhary пише: > (In my experience) > > Does the host-node have working IPv6 configured on it? If yes, > > Then you can just do, > > vzctl set --ipadd -- save > > and the container too will have working IPv6. > > If the host-node does not have working IPv6, then you can just configure > any address of the IPv6 range on the host-node > > > On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: > >> Trying to setup IPv6 for CentOS7 CT. >> Seems original documentation outdated a bit (https://wiki.openvz.org/IPv6 >> ). >> Is there updated information? >> >> Thank you! >> >> >> -- >> Oleksiy >> ___ >> Users mailing list >> Users@openvz.org >> https://lists.openvz.org/mailman/listinfo/users >> > > > -- > Thanks, > Arjit Chaudhary > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6, openVZ7, CentOS7
(In my experience) Does the host-node have working IPv6 configured on it? If yes, Then you can just do, vzctl set --ipadd -- save and the container too will have working IPv6. If the host-node does not have working IPv6, then you can just configure any address of the IPv6 range on the host-node On Thu, Dec 15, 2022 at 4:15 AM UNLIM.SRV wrote: > Trying to setup IPv6 for CentOS7 CT. > Seems original documentation outdated a bit (https://wiki.openvz.org/IPv6 > ). > Is there updated information? > > Thank you! > > > -- > Oleksiy > ___ > Users mailing list > Users@openvz.org > https://lists.openvz.org/mailman/listinfo/users > -- Thanks, Arjit Chaudhary ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] IPv6, openVZ7, CentOS7
Trying to setup IPv6 for CentOS7 CT. Seems original documentation outdated a bit (https://wiki.openvz.org/IPv6). Is there updated information? Thank you! -- Oleksiy ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 problem
On 6/11/21 12:02 PM, mailingl...@tikklik.nl wrote: > Any idees what can be wrong. > > I can add a ipv6 ip to any container, but one > > vzctl set 201 --ipadd 2a00:1bd0:740:xxx --save > > Adding IP address(es): 2a00:1bd0:740: > > SIOCSIFADDR: Permission denied which kernel version is used on your node? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 problem
Never mind, found it Was a older vps container that had ipv6 disabled -Oorspronkelijk bericht- Van: users-boun...@openvz.org Namens Vasily Averin Verzonden: vrijdag 11 juni 2021 11:28 Aan: users@openvz.org Onderwerp: Re: [Users] ipv6 problem On 6/11/21 12:02 PM, mailingl...@tikklik.nl wrote: > Any idees what can be wrong. > > I can add a ipv6 ip to any container, but one > > vzctl set 201 --ipadd 2a00:1bd0:740:xxx --save > > Adding IP address(es): 2a00:1bd0:740: > > SIOCSIFADDR: Permission denied which kernel version is used on your node? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] ipv6 problem
Any idees what can be wrong. I can add a ipv6 ip to any container, but one vzctl set 201 --ipadd 2a00:1bd0:740:xxx --save Adding IP address(es): 2a00:1bd0:740: SIOCSIFADDR: Permission denied Thanks Steffan ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 connectivity to http://ftp.openvz.org
Hi, On 08:14 Sun 22 Nov , J.E. wrote: > > Then I tried pulling a random template. Was over 20 MB/s at one point then > averaged out between 4 MB & 6 MB/s. I've seen it steady at 2 MB/s before > (both v4 and v6) just for vztmpl-dl. Getting there! JFYI: there are two primary download site: in USA (Seattle): download.openvz.org in Europe (Switzerland): eu.download.openvz.org and also we have hundred OpenVZ mirrors maintained by volunteers: https://mirrors.openvz.org/ Pick the nearest one to get max download speed. Sergey ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 connectivity to http://ftp.openvz.org
root@hyperion:~# wget -O - http://ftp.openvz.org/debian/archive.key && rm -rf archive.key --2015-11-22 02:43:10-- http://ftp.openvz.org/debian/archive.key Resolving ftp.openvz.org (ftp.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to ftp.openvz.org (ftp.openvz.org)|2620:e6::104:11|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 1694 (1.7K) [text/plain] Saving to: 'STDOUT' 100%[==>] 2015-11-22 02:43:10 (510 MB/s) - written to stdout [1694/1694] Then I tried pulling a random template. Was over 20 MB/s at one point then averaged out between 4 MB & 6 MB/s. I've seen it steady at 2 MB/s before (both v4 and v6) just for vztmpl-dl. Getting there! root@hyperion:~# wget -N http://download.openvz.org/template/precreated/centos-6-x86_64-devel.tar.gz && rm -rf centos-6* --2015-11-22 03:06:09-- http://download.openvz.org/template/precreated/centos-6-x86_64-devel.tar.gz Resolving download.openvz.org (download.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to download.openvz.org (download.openvz.org)|2620:e6::104:11|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 264526360 (252M) [application/x-gzip] Saving to: 'centos-6-x86_64-devel.tar.gz' 100%[==>] 2015-11-22 03:06:57 (5.26 MB/s) - 'centos-6-x86_64-devel.tar.gz' -- traceroute to download.openvz.org (2620:e6::104:11) from 2607:ff68:106:f:a:d:e:d, 30 hops max, 24 byte packets 1 2607:ff68:106::3 (2607:ff68:106::3) 0.179 ms 0.071 ms 0.059 ms 2 te3-3.core1.bdr1.dllstx3.dallas-idc.com (2607:ff68:1:a::1) 1.767 ms 1.754 ms 1.46 ms 3 2607:ff68:1:6::11 (2607:ff68:1:6::11) 3.589 ms 2.339 ms 1.842 ms 4 2607:ff68:1:6::72 (2607:ff68:1:6::72) 1.128 ms 2.012 ms 0.837 ms 5 2001:550:2:7d::1 (2001:550:2:7d::1) 1.106 ms 1.168 ms 1.044 ms 6 te0-0-0-26.ccr22.dfw01.atlas.cogentco.com (2001:550:0:1000::9a36:2e2d) 1.13 ms 1.229 ms 1.106 ms 7 be2433.ccr22.mci01.atlas.cogentco.com (2001:550:0:1000::9a36:3d6) 11.295 ms 12.329 ms 11.289 ms 8 be2130.ccr22.den01.atlas.cogentco.com (2001:550:0:1000::9a36:1a79) 23.974 ms 23.549 ms 23.057 ms 9 be2127.ccr21.slc01.atlas.cogentco.com (2001:550:0:1000::9a36:1946) 33.743 ms 34.359 ms 33.44 ms 10 be2085.ccr21.sea02.atlas.cogentco.com (2001:550:0:1000::9a36:2c5) 54.83 ms 54.405 ms 54.56 ms 11 be2481.rcr11.sea05.atlas.cogentco.com (2001:550:0:1000::9a36:1982) 56.466 ms 55.926 ms 55.816 ms 12 te0-0-2-3.rcr11.sea03.atlas.cogentco.com (2001:550:0:1000::9a36:1b9) 55.561 ms 55.433 ms 55.385 ms 13 te0-0-2-2.agr12.sea03.atlas.cogentco.com (2001:550:0:1000::9a18:efe) 55.497 ms 55.894 ms 56.146 ms 14 te0-0-2-3.nr12.b022847-3.sea03.atlas.cogentco.com (2001:550:0:1000::9a18:1322) 56.457 ms 56.285 ms 56.248 ms 15 2001:550:2:30::2:3 (2001:550:2:30::2:3) 55.71 ms 55.857 ms 55.678 ms 16 2620:e6::105:224 (2620:e6::105:224) 56.011 ms 55.2 ms 55.056 ms 17 download.openvz.org (2620:e6::104:11) 55.224 ms 55.034 ms 55.248 ms John Edel On Wed, 18 Nov 2015, Kir Kolyshkin wrote: It seems it's working now. If it's not working for you, please provide a traceroute6 output. Kir On 11/13/2015 07:03 AM, CoolCold wrote: Hello! Looks like ftp.openvz.org resolvs via ipv6 too, but not working well: root@mu2 /home/coolcold # wget -O - 'http://ftp.openvz.org/debian/archive.key'|apt-key add - --2015-11-13 17:59:40-- http://ftp.openvz.org/debian/archive.key Resolving ftp.openvz.org (ftp.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to ftp.openvz.org (ftp.openvz.org)|2620:e6::104:11|:80... failed: Connection timed out. Connecting to ftp.openvz.org (ftp.openvz.org)|199.115.104.11|:80... connected. checking with telnet: root@mu2 /home/coolcold # telnet -6 ftp.openvz.org 80 Trying 2620:e6::104:11... telnet: Unable to connect to remote host: Connection timed out and yandex is ok: coolcold@mu2:~/gits/flashcache$ telnet -6 www.ya.ru 80 Trying 2a02:6b8::3... Connected to ya.ru. Escape character is '^]'. ^] telnet> quit Connection closed. should you disable ipv6 resolve? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 connectivity to http://ftp.openvz.org
It seems it's working now. If it's not working for you, please provide a traceroute6 output. Kir On 11/13/2015 07:03 AM, CoolCold wrote: Hello! Looks like ftp.openvz.org resolvs via ipv6 too, but not working well: root@mu2 /home/coolcold # wget -O - 'http://ftp.openvz.org/debian/archive.key'|apt-key add - --2015-11-13 17:59:40-- http://ftp.openvz.org/debian/archive.key Resolving ftp.openvz.org (ftp.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to ftp.openvz.org (ftp.openvz.org)|2620:e6::104:11|:80... failed: Connection timed out. Connecting to ftp.openvz.org (ftp.openvz.org)|199.115.104.11|:80... connected. checking with telnet: root@mu2 /home/coolcold # telnet -6 ftp.openvz.org 80 Trying 2620:e6::104:11... telnet: Unable to connect to remote host: Connection timed out and yandex is ok: coolcold@mu2:~/gits/flashcache$ telnet -6 www.ya.ru 80 Trying 2a02:6b8::3... Connected to ya.ru. Escape character is '^]'. ^] telnet> quit Connection closed. should you disable ipv6 resolve? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] ipv6 connectivity to http://ftp.openvz.org
Hello! Looks like ftp.openvz.org resolvs via ipv6 too, but not working well: root@mu2 /home/coolcold # wget -O - 'http://ftp.openvz.org/debian/archive.key'|apt-key add - --2015-11-13 17:59:40-- http://ftp.openvz.org/debian/archive.key Resolving ftp.openvz.org (ftp.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to ftp.openvz.org (ftp.openvz.org)|2620:e6::104:11|:80... failed: Connection timed out. Connecting to ftp.openvz.org (ftp.openvz.org)|199.115.104.11|:80... connected. checking with telnet: root@mu2 /home/coolcold # telnet -6 ftp.openvz.org 80 Trying 2620:e6::104:11... telnet: Unable to connect to remote host: Connection timed out and yandex is ok: coolcold@mu2:~/gits/flashcache$ telnet -6 www.ya.ru 80 Trying 2a02:6b8::3... Connected to ya.ru. Escape character is '^]'. ^] telnet> quit Connection closed. should you disable ipv6 resolve? -- Best regards, [COOLCOLD-RIPN] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 connectivity to http://ftp.openvz.org
On 11/13/2015 07:03 AM, CoolCold wrote: Hello! Looks like ftp.openvz.org resolvs via ipv6 too, but not working well: Hi, We are aware of the problem and let the admins know, still waiting for them to reply. Anyway, thanks for reporting Kir. root@mu2 /home/coolcold # wget -O - 'http://ftp.openvz.org/debian/archive.key'|apt-key add - --2015-11-13 17:59:40-- http://ftp.openvz.org/debian/archive.key Resolving ftp.openvz.org (ftp.openvz.org)... 2620:e6::104:11, 199.115.104.11 Connecting to ftp.openvz.org (ftp.openvz.org)|2620:e6::104:11|:80... failed: Connection timed out. Connecting to ftp.openvz.org (ftp.openvz.org)|199.115.104.11|:80... connected. checking with telnet: root@mu2 /home/coolcold # telnet -6 ftp.openvz.org 80 Trying 2620:e6::104:11... telnet: Unable to connect to remote host: Connection timed out and yandex is ok: coolcold@mu2:~/gits/flashcache$ telnet -6 www.ya.ru 80 Trying 2a02:6b8::3... Connected to ya.ru. Escape character is '^]'. ^] telnet> quit Connection closed. should you disable ipv6 resolve? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] IPv6
Recently IPv6 quit working on my Openvz CentOS 6 box. No longer works on host or containers. I imagine it was after a yum update. Whats weird is if I reboot the OpenVZ host machine IPv6 starts to work again on the host and the containers for about 5 minutes but then quits again. Any ideas? I installed following these directions. https://openvz.org/Quick_installation With some changes found here to allow bridged containers and IPv6. https://openvz.org/Quick_Installation_CentOS_6 http://openvz.org/Virtual_Ethernet_device https://openvz.org/IPv6 ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6
Greetings, - Original Message - Recently IPv6 quit working on my Openvz CentOS 6 box. No longer works on host or containers. I imagine it was after a yum update. Whats weird is if I reboot the OpenVZ host machine IPv6 starts to work again on the host and the containers for about 5 minutes but then quits again. Any ideas? I haven't used IPv6 at all so I'm ignorant about it... but you really didn't give much in the way of details that will probably be helpful to others who are familiar with IPv6. What kernel version are you running? What version of vzctl? TYL, -- Scott Dowdle 704 Church Street Belgrade, MT 59714 (406)388-0827 [home] (406)994-3931 [work] ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, can you ping the host machine from within the container? What does ip - -6 r l say? Is there anything in /var/log/messages regarding IPv6? In my host machines I had to do that in order to get IPv6 working properly: for proxy_ndp in /proc/sys/net/ipv6/conf/eth*/proxy_ndp; do echo 1 $proxy_ndp; done On 02/03/2015 06:04 PM, Matt wrote: Recently IPv6 quit working on my Openvz CentOS 6 box. No longer works on host or containers. I imagine it was after a yum update. Whats weird is if I reboot the OpenVZ host machine IPv6 starts to work again on the host and the containers for about 5 minutes but then quits again. Any ideas? I installed following these directions. https://openvz.org/Quick_installation With some changes found here to allow bridged containers and IPv6. https://openvz.org/Quick_Installation_CentOS_6 http://openvz.org/Virtual_Ethernet_device https://openvz.org/IPv6 ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users - -- Best regards Kevin Holly - r...@hallowe.lt - http://hallowe.lt/ -BEGIN PGP SIGNATURE- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAEBAgAGBQJU0R/DAAoJELAaqP3QtzpM10EH/1tDnPpTx1QdAFeckNryDc2d VORhi0aehYrIVb3ZGqjyWz7czAd1CrTSQ8bAgXD0c4ADlVf7O8ozOxaJFapB+TOB JolO/S8191yx3Dj+Ax7Olo9dk42rzN627WXmNy8ufscvM5Pma6oql3UpUJmbCdxo o0zuaQt6qGN/NxnIt/x6/gHIQH9DxHlQFKTG4BFPP7Wm2WaV8miVbmgs/XqHYW6s 9PuO/C4sg476dWFSK+Smsw2W0gas4f5+MdQLRtRNJSUaZbfjeG2mWwkO9pVj19Lx oNeCzPsxD2lbgsbOJm3kEg+AMT0KPsTeKzmaIes126J5HO4C4v0aN1VaoTNOQdQ= =U6Bx -END PGP SIGNATURE- ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6
can you ping the host machine from within the container? What does ip - -6 r l say? Is there anything in /var/log/messages regarding IPv6? Yes I can ping my own IPv6 IP. In my host machines I had to do that in order to get IPv6 working properly: for proxy_ndp in /proc/sys/net/ipv6/conf/eth*/proxy_ndp; do echo 1 $proxy_ndp; done # grep ipv6 /etc/sysctl.conf net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 Again this was all working fine since it was put in about year ago. Just starting acting up in last month I am guessing. I know it worked fine 2 months ago. Also, if I do service network restart on a container IPv6 will start working again for about 5 minutes. Same for host. Recently IPv6 quit working on my Openvz CentOS 6 box. No longer works on host or containers. I imagine it was after a yum update. Whats weird is if I reboot the OpenVZ host machine IPv6 starts to work again on the host and the containers for about 5 minutes but then quits again. Any ideas? I installed following these directions. https://openvz.org/Quick_installation With some changes found here to allow bridged containers and IPv6. https://openvz.org/Quick_Installation_CentOS_6 http://openvz.org/Virtual_Ethernet_device https://openvz.org/IPv6 ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
[Users] IPv6
I used this guide to install OpenVZ. https://openvz.org/Quick_Installation_CentOS_6 I am setting certain containers up as bridged so I can run IPv6 on them. I have IPv6 working on the host but I cannot get it to work on the container. The host and container can IPv6 ping each other but the container cannot ping the IPv6 gateway or anything else. Any ideas? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6
Turn this in sysctl.conf net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 Also check your ip6tables in host . On 07/10/2014 05:15 PM, Matt wrote: I used this guide to install OpenVZ. https://openvz.org/Quick_Installation_CentOS_6 I am setting certain containers up as bridged so I can run IPv6 on them. I have IPv6 working on the host but I cannot get it to work on the container. The host and container can IPv6 ping each other but the container cannot ping the IPv6 gateway or anything else. Any ideas? ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users -- Dragomir Zhelev CEO Delta SoftMedia OOD Phone: +359 2 44 84 165 Cellular: +359 895 66 99 79 E-mail: dr...@delta.bg Web: Delta.BG http://delta.bg ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] IPv6
It was an ip6tables issue. Thanks. On Thu, Jul 10, 2014 at 10:07 AM, Dragomir Zhelev dr...@delta.bg wrote: Turn this in sysctl.conf net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.proxy_ndp = 1 Also check your ip6tables in host . On 07/10/2014 05:15 PM, Matt wrote: I used this guide to install OpenVZ. https://openvz.org/Quick_Installation_CentOS_6 I am setting certain containers up as bridged so I can run IPv6 on them. I have IPv6 working on the host but I cannot get it to work on the container. The host and container can IPv6 ping each other but the container cannot ping the IPv6 gateway or anything else. Any ideas? ___ Users mailing listUsers@openvz.orghttps://lists.openvz.org/mailman/listinfo/users -- Dragomir Zhelev CEO Delta SoftMedia OOD Phone: +359 2 44 84 165 Cellular: +359 895 66 99 79 E-mail: dr...@delta.bg Web: Delta.BG http://delta.bg ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://lists.openvz.org/mailman/listinfo/users
Re: [Users] ipv6 on container
On Wed, 2010-11-10 at 11:57 -0600, Hospedaje Web y Servidores Dedicados wrote: hi, i want to setup the ipv6 on a container, my main node has my /48 installed, and inside the CT i do --Container-- [root@ipv6 ~]# modprobe ipv6 FATAL: Could not load /lib/modules/2.6.18-164.10.1.el5.028stab067.4PAE/modules.dep: No such file or directory [root@ipv6 ~]# mkdir -p /lib/modules/2.6.18-164.10.1.el5.028stab067.4PAE/ [root@ipv6 ~]# depmod -a [root@ipv6 ~]# modprobe ipv6 FATAL: Module ipv6 not found. how to enable It's probably already enabled. If it's enabled in the host node it's going to be enabled in the guest. Run ip -6 addr ls in the guest. You should see something like this: [root@yelm ~]# ip -6 addr ls 13: eth0: BROADCAST,MULTICAST,UP,LOWER_UP mtu 1500 qlen 1000 inet6 2001:4830:3000:8200:204:8ff:fecd:263d/64 scope global dynamic valid_lft 2591958sec preferred_lft 604758sec inet6 fe80::204:8ff:fecd:263d/64 scope link valid_lft forever preferred_lft forever 15: lo: LOOPBACK,UP,LOWER_UP mtu 16436 inet6 ::1/128 scope host valid_lft forever preferred_lft forever You see anything with inet6 addresses, you've got it enabled. It may not be configured, but you've got it enabled. -- Ing. Alejandro M. --- Hospedaje Web y Servidores Dedicados http://www.dedicados.com.mx --- ven...@dedicados.com.mx --- Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] ipv6 on container
hi, i want to setup the ipv6 on a container, my main node has my /48 installed, and inside the CT i do --Container-- [root@ipv6 ~]# modprobe ipv6 FATAL: Could not load /lib/modules/2.6.18-164.10.1.el5.028stab067.4PAE/modules.dep: No such file or directory [root@ipv6 ~]# mkdir -p /lib/modules/2.6.18-164.10.1.el5.028stab067.4PAE/ [root@ipv6 ~]# depmod -a [root@ipv6 ~]# modprobe ipv6 FATAL: Module ipv6 not found. how to enable -- Ing. Alejandro M. --- Hospedaje Web y Servidores Dedicados http://www.dedicados.com.mx --- ven...@dedicados.com.mx --- ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] ipv6 on container
On Wed, 10 Nov 2010, Hospedaje Web y Servidores Dedicados wrote: hi, i want to setup the ipv6 on a container, my main node has my /48 Have you looked at: http://wiki.openvz.org/VEs_and_HNs_in_same_subnets Antonio Querubin e-mail/xmpp: t...@lava.net ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] ipv6 on container
hello, On Thu, 2011-02-03 at 04:03 -1000, Antonio Querubin wrote: On Wed, 10 Nov 2010, Hospedaje Web y Servidores Dedicados wrote: hi, i want to setup the ipv6 on a container, my main node has my /48 Have you looked at: http://wiki.openvz.org/VEs_and_HNs_in_same_subnets I confirm this is working no trouble.. Note: If you have container dual stack (IPV4,IPV6) but NOT all container on the IPV4 subnet, you need to define a second bridge on the host (with the IPV6 number) and container with a second interface (eth1) attached to the host second bridge. Having the container set with one interface carrying both IPV6+IPV6, but not all the container on the same IPV4 subnet make the routing quite unreliable. Antonio Querubin e-mail/xmpp: t...@lava.net ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users -- A bientôt == Jean-Marc Pigeon Internet: j...@safe.ca SAFE Inc. Phone: (514) 493-4280 Fax: (514) 493-1946 Clement, 'a kiss solution' to get rid of SPAM (at last) Clement' Home base http://www.clement.safe.ca; == smime.p7s Description: S/MIME cryptographic signature ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6: PMTU disc is broken in stable RHEL5 kernel for VETH
Hi, Some days ago I submitted a bug to point out a problem we encountered in path MTU discovery not working properly for IPv6 VETH interfaces: http://bugzilla.openvz.org/show_bug.cgi?id=1675 This report didn't receive any feedback for now. Could someone have a look at this problem ? PMTU discovery is a mandatory feature for proper IPv6 functionnality (apart from crippling down the MTU globally on the interface). According to our tests done so far, the problem can be reproduced in any bridged VETH configuration, whatever interface is bridged in (a bare-metal physical one, a bonding, a VLAN, or even a VLAN over a bonding). However, it does not show up with VENET interfaces in the distribution-standard config (arp-proxy-based routed mode); it appears to be veth-specific. -- Benoit BRANCIARD CRIR - SIS Centre de Ressources Informatiques et du Réseau, Service Infrastructures http://crir.univ-paris1.fr Université Paris 1 Panthéon-Sorbonne Tel. 01 44 07 89 68 -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 with OpenVZ; new Owl ISOs and templates
Hi, Simon, a user of and a contributor to Openwall GNU/*/Linux (Owl), wrote the following how-to on setting up OpenVZ containers reachable over IPv6: https://azuma.kaizo.org/simonb/openvz+ipv6.php This describes the following setup: * You have 'a' machine, with a single public facing Internet address (IPv4) * This machine has a public facing IPv6 address range, in this case a /64. * You have IPv4 and IPv6 working on the machine already * You run OpenVZ (or similar) VM's which have rfc1918 addresses * You use NAT/IPTables to route traffic to those OpenVZ hosts * You *wish* to allocate some Internet routable IPv6 addresses to the VM's More context to it (also on a hosting provider in the UK allowing you to setup Owl/OpenVZ in a Linux KVM based VPS with IPv4 + IPv6 connectivity): http://www.openwall.com/lists/owl-users/2010/07/29/1 Meanwhile, we have fresh Owl ISOs (with the latest OpenVZ rhel5 kernels) and precreated OpenVZ container templates: lftp mirrors.kernel.org:/openwall/Owl/current ls iso vztemplate | fgrep 0729 -rw-r--r-- 455M 2010-07-29 02:53 Owl-current-20100729-i686.iso.gz -rw-r--r-- 460M 2010-07-29 03:37 Owl-current-20100729-x86_64.iso.gz -rw-r--r-- 110M 2010-07-29 05:06 owl-current-20100729-i686.tar.gz -rw-r--r-- 112M 2010-07-29 04:43 owl-current-20100729-x86_64.tar.gz As usual, the ISOs are live + installable (and they will offer ext4 now), and the templates are full Owl installs (e.g. capable of rebuilding Owl from source). Any feedback is welcome. Alexander ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 tables state module in 2.6.26-2-openvz-amd64
Hi, I'm running OpenVZ HW node on Debian Lenny with Debian stock kernel 2.6.26-2-openvz-amd64 When I try to use ip6tables ... -m state I get: ip6tables: Invalid argument and HW node kernel prints: can't load conntrack support for proto=10 Have changed something since 2.6.18? My ip6tables were taken from 2.6.18-128.2.1.el5.028stab064.8 where they works just fine. Piece of FW definition: /sbin/ip6tables -N STATE /sbin/ip6tables -A STATE -m state --state RELATED,ESTABLISHED -j ACCEPT ip6tables: Invalid argument Piece of /etc/vz.conf: ## IPv4 iptables kernel modules IPTABLES=ipt_REJECT ipt_tos ipt_limit ipt_multiport iptable_filter iptable_mangle ipt_TCPMSS ipt_tcpmss ipt_ttl ipt_length ipt_LOG ipt_state ipt_conntrack ip_conntrack ip_conntrack_ftp xt_state ## Enable IPv6 IPV6=yes ## IPv6 ip6tables kernel modules IP6TABLES=ip6_tables ip6table_filter ip6table_mangle ip6t_REJECT ip6t_hl ip6t_rt xt_conntrack nt_conntrack nf_conntrack_ipv6 xt_state cat /boot/config-2.6.26-2-openvz-amd64 | grep IP6 CONFIG_IPV6_MIP6=m CONFIG_IP6_NF_QUEUE=m CONFIG_IP6_NF_IPTABLES=m CONFIG_IP6_NF_MATCH_RT=m CONFIG_IP6_NF_MATCH_OPTS=m CONFIG_IP6_NF_MATCH_FRAG=m CONFIG_IP6_NF_MATCH_HL=m CONFIG_IP6_NF_MATCH_IPV6HEADER=m CONFIG_IP6_NF_MATCH_AH=m CONFIG_IP6_NF_MATCH_MH=m CONFIG_IP6_NF_MATCH_EUI64=m CONFIG_IP6_NF_FILTER=m CONFIG_IP6_NF_TARGET_LOG=m CONFIG_IP6_NF_TARGET_REJECT=m CONFIG_IP6_NF_MANGLE=m CONFIG_IP6_NF_TARGET_HL=m CONFIG_IP6_NF_RAW=m CONFIG_SLIP_MODE_SLIP6=y Any suggestions please? -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 Support in VE's
On Thu, 26 Nov 2009, Michael H. Warfield wrote: Hey hey... On Wed, 2009-11-25 at 14:25 -1000, Antonio Querubin wrote: Care to share your IPv6 configs for the VEs with the rest of us? The wiki's IPv6 examples don't seem to work for us here. Sure. Not problem. They're small enough I'll just do them in-line It works! One problem left to figure out is how to disable the automatic munging of the GATEWAY in each VE's /etc/sysconfig/network file. For now I'm forcing it in each VE's ifcfg-eth0 file. here. I gave up on the IPv6 stuff in the wiki ages ago as simply going way off in the wrong direction. Too much fixation on the vnet device. I think this topic came up years ago on the list and all I heard back was excuses about why it didn't support MAC addresses and how we didn't need MAC addresses and all kinds of IPv4 think wrt IPv6. Whadeva... Dump the vnet cruft and forget about it. Concur. Antonio Querubin 808-545-5282 x3003 e-mail/xmpp: t...@lava.net ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 Support in VE's
Hello, I have OpenVZ setup and running with ipv4 without any issues. I would like to get ipv6 address to the ve's My network currently has ipv6 and the hardware nodes have ipv6 addresses assigned to them. I currently have ipv6 built into the kernel and also enabled in /etc/vz/vz.conf If I add an ipv6 address to a VE when i try to start it i get the following ... virt1 linux # vzctl start 46 Starting VE ... VE is mounted Adding IP address(es): 192.168.4.46 2001:470:9002:2::46 RTNETLINK answers: No such device vps-net_add ERROR: Unable to add route /sbin/ip route add 2001:470:9002:2::46 dev venet0 VE start failed Stopping VE ... VE was stopped VE is unmounted Does anybody know why I might be getting this and what else I can check. The next thing I would try is running ipv6 as a kernel module but it would be nice if this wasn't necessary. my vzctl version is ... vzctl version 3.0.22 Cheers, Matt. smime.p7s Description: S/MIME Cryptographic Signature ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ?? *SOLVED*
Jan Tomasek a écrit : Benoit Branciard wrote: IPv6 forwarding is still mandatory, but this implies manual configuration of IP address, netmask and default route on hardware node. This last point may be annoying: in our case the default route is hardware-dependent, so if some day we need to replace the router (or the router interface), default route will become invalid and manual reconfiguration of all openVZ hardware nodes will be needed. Too bad Linux kernel doesn't allow enabling forwarding without disabling autoconfiguration. I'm not sure, but I think that my setup is router independent. For my virtual servers I got prefix 2001:718:1:e::/64 (which is unbelivable waste of IP range but they say this is normal in IPv6). This network block is asigned to dedicated VLAN. IPv6 Gateway for all physical systems in that network is 2001:718:1:e::1. Here's the clue: you have been assigned a static gateway IP address by your network provider. So no problem. In our case we are operating our nework, and have chosen to not set static gateway IP adresses, relying on autoconfiguration to discover the EUI-64 (MAC-dependant) default route IP. That sounded nice (nothing to hardcode) until openVZ came on. Maybe we could change our router config policy, and assign static IP addresses to router interfaces. But that's not trivial operation, involving network downtime, and we wont do that without motivated reasons. -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ?? *SOLVED*
Benoit Branciard a écrit : - IPv6 VS doesn't work !!! (ping6 works *only* between VS and hardware node, not from external sources; VS has IPv6 address correctly defined, as per ifconfig). For list archives: It was caused by a small bug in vzctl scripts which handle NEIGHBOUR_DEVS=detect feature introduced in vzctl 3.0.22 : neighbour devices were not detected for IPv6. Fix is here: http://git.altlinux.org/people/ldv/packages/?p=vzctl.git;a=commitdiff;h=maint Thanks to Jan, Kir and Dmitry ! I suspected it may be useful to set sysctl net.ipv6.conf.iface.forwarding to 1, but : - this turns the box in router mode, disabling RA acceptance from default router (annoying) IPv6 forwarding is still mandatory, but this implies manual configuration of IP address, netmask and default route on hardware node. This last point may be annoying: in our case the default route is hardware-dependent, so if some day we need to replace the router (or the router interface), default route will become invalid and manual reconfiguration of all openVZ hardware nodes will be needed. Too bad Linux kernel doesn't allow enabling forwarding without disabling autoconfiguration. -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ?? *SOLVED*
Benoit Branciard wrote: I suspected it may be useful to set sysctl net.ipv6.conf.iface.forwarding to 1, but : - this turns the box in router mode, disabling RA acceptance from default router (annoying) IPv6 forwarding is still mandatory, but this implies manual configuration of IP address, netmask and default route on hardware node. This last point may be annoying: in our case the default route is hardware-dependent, so if some day we need to replace the router (or the router interface), default route will become invalid and manual reconfiguration of all openVZ hardware nodes will be needed. Too bad Linux kernel doesn't allow enabling forwarding without disabling autoconfiguration. I'm not sure, but I think that my setup is router independent. For my virtual servers I got prefix 2001:718:1:e::/64 (which is unbelivable waste of IP range but they say this is normal in IPv6). This network block is asigned to dedicated VLAN. IPv6 Gateway for all physical systems in that network is 2001:718:1:e::1. My setup on HW node is: iface eth0 inet6 static post-up /sbin/sysctl -w net.ipv6.conf.eth0.autoconf=0 post-up /sbin/sysctl -w net.ipv6.conf.all.forwarding=1 address 2001:718:1:e::23:3254 gateway 2001:718:1:e::1 netmask 64 I'm trying to stay away of MAC dependent automaticaly asigned IPs because of dependence on hardware. I hope this might you, if needed I might try to ask our network specialists about more details... Best regards -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ??
Can you give us the the output of /sbin/ip a l and fgrep ADDRESS /etc/vz/conf/*.conf command run on your hardware node? Perhaps the problem is that the network interface(s) that is/are present on the hardware node do not belong to the same IP subnets as your VEs. Dmitry, Maybe it makes sense to add a warning if vz_get_neighbour_devs() returns an empty list, with the URL to a wiki page with long explanation? Jan Tomasek wrote: Hi, problem was caused by setting: # Controls which interfaces to send ARP requests and modify APR tables # on. NEIGHBOUR_DEVS=detect this option arived with vzctl version 3.0.22 when I was upgrading from 3.0.18-1dso1. After I removed that option and restarted HW node all IPv6 hosts get imediately online. Ufff! :) ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ??
Hi, problem was caused by setting: # Controls which interfaces to send ARP requests and modify APR tables # on. NEIGHBOUR_DEVS=detect this option arived with vzctl version 3.0.22 when I was upgrading from 3.0.18-1dso1. After I removed that option and restarted HW node all IPv6 hosts get imediately online. Ufff! :) -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 ??
Temporarily giving up messing with veth devices (forgot dhcpd server for now), I concentrated on setting up a basic VS with both IPv4 and IPv6 addresses, using standard venet device. I'm using Debian Etch hardware node with debian.systs.org packages. So I did: - install packages and reboot as necessary : fzakernel-2.6.18-686 vzctl vzctl-ostmpl-debian vzdump vzprocps vzquota - ensure /etc/sysctl.conf contains : net.ipv4.conf.default.forwarding = 1 net.ipv4.conf.all.rp_filter = 1 kernel.sysrq = 1 net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 - ensure /etc/vz/vz.conf contains: IPV6=yes - create VS : vzctl create 112 --ipadd XXX.YYY.ZZZ.12 --ipadd xxx:yyy:::12 --hostname brahma-vps112 (default template is debian-4.0-i386-minimal, hardware node has only one physical interface activated, on the same subnet as VS) - start VS : vzctl start 112 Result: - IPv4 VS works as expected (ping succeeds from hardware node, external server in same subnet, external server on another subnet). - IPv6 VS doesn't work !!! (ping6 works *only* between VS and hardware node, not from external sources; VS has IPv6 address correctly defined, as per ifconfig). Am I missing something ? I suspected it may be useful to set sysctl net.ipv6.conf.iface.forwarding to 1, but : - this turns the box in router mode, disabling RA acceptance from default router (annoying) - this doesn't work either !! -- Ce message a ete verifie par MailScanner pour des virus ou des polluriels et rien de suspect n'a ete trouve. ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ??
Hi, for official IPv6 i'm useing sixxs as tunnelbroker, these steps i've done connect a Debian OpenVZ system to a IPv6 Network for the VE with a venet0 interface: 1) Setup an IPv6 Tunnel (- https://noc.sixxs.net/ ) Relevant IPv6 settings in /etc/network/interfaces [...] # device: sixxs ipv6 tunnel with static IPv6 auto sixxs iface sixxs inet6 v4tunnel address your_assigned_IPv6_ADDRESS netmask 64 endpoint IPv4_ADDRESS_of_tunnelbroker ttl 64 up ip link set mtu 1280 dev sixxs up ip route add default via IPv6_ADDRESS_of_tunnelbroker dev sixxs [...] VE_0$ ifup sixxs 2) Setup OpenVZ with IPv6 : # enable IPv6 forwarding for all Interfaces VE_0$ sysctl -q -w net.ipv6.conf.all.forwarding=1 # enable IPv6 in /etc/vz/vz.conf - IPV6=yes # and restart OpenVZ Subsystem, so venet has a IPv6 Address VE_0$ /etc/init.d/vz restart # give a VE an IPv6 address, you need a IPv6 subnet ( https://noc.sixxs.net/ ) VE_0$ vzctl set VEID --ipadd IPv6_ADDRESS [--yes] 3) Test it If you connected to an official IPv6 network, you can test it, by pinging debian.systs.org ( 2001:6f8:109a::1a01 ) or visit IPv6 sites like http://www.kame.net and see the dancing turtle ;-) Bye, Thorsten -- Thorsten Schifferdecker [EMAIL PROTECTED] ---//--- Am Do, 24.01.2008, 18:29, schrieb Benoit Branciard: Temporarily giving up messing with veth devices (forgot dhcpd server for now), I concentrated on setting up a basic VS with both IPv4 and IPv6 addresses, using standard venet device. I'm using Debian Etch hardware node with debian.systs.org packages. So I did: - install packages and reboot as necessary : fzakernel-2.6.18-686 vzctl vzctl-ostmpl-debian vzdump vzprocps vzquota - ensure /etc/sysctl.conf contains : net.ipv4.conf.default.forwarding = 1 net.ipv4.conf.all.rp_filter = 1 kernel.sysrq = 1 net.ipv4.conf.default.send_redirects = 1 net.ipv4.conf.all.send_redirects = 0 - ensure /etc/vz/vz.conf contains: IPV6=yes - create VS : vzctl create 112 --ipadd XXX.YYY.ZZZ.12 --ipadd xxx:yyy:::12 --hostname brahma-vps112 (default template is debian-4.0-i386-minimal, hardware node has only one physical interface activated, on the same subnet as VS) - start VS : vzctl start 112 Result: - IPv4 VS works as expected (ping succeeds from hardware node, external server in same subnet, external server on another subnet). - IPv6 VS doesn't work !!! (ping6 works *only* between VS and hardware node, not from external sources; VS has IPv6 address correctly defined, as per ifconfig). Am I missing something ? I suspected it may be useful to set sysctl net.ipv6.conf.iface.forwarding to 1, but : - this turns the box in router mode, disabling RA acceptance from default router (annoying) - this doesn't work either !! ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 ??
Hello Benoit, Temporarily giving up messing with veth devices (forgot dhcpd server for now), I concentrated on setting up a basic VS with both IPv4 and IPv6 addresses, using standard venet device. [...] Result: - IPv4 VS works as expected (ping succeeds from hardware node, external server in same subnet, external server on another subnet). - IPv6 VS doesn't work !!! (ping6 works *only* between VS and hardware node, not from external sources; VS has IPv6 address correctly defined, as per ifconfig). Am I missing something ? I suspected it may be useful to set sysctl net.ipv6.conf.iface.forwarding to 1, but : - this turns the box in router mode, disabling RA acceptance from default router (annoying) - this doesn't work either !! Very interesting! I'm having exactly same problem here. IPv6 was working perfectly for me after some problems before several months. Now I had to reboot my HW node and IPv6 is gone. When I try to ping VE from real world I'm getting: [EMAIL PROTECTED]:~$ ping6 2001:718:1:e::23:3257 PING 2001:718:1:e::23:3257(2001:718:1:e::23:3257) 56 data bytes From 2001:718:1:101::1 icmp_seq=0 Destination unreachable: Address unreachable From 2001:718:1:101::1 icmp_seq=3 Destination unreachable: Address unreachable From HW node to VE or from one VE to another VE is IPv6 working fine. I think that HW node didn't sent some info to it's IPv6 gateway about presence of new IPv6 address. Sadly I'm clue less how to better debug this. But! I've discovered trick. Run alternate version of this on your HW node: ifconfig eth0 add 2001:718:1:e::23:3257/64 sleep 5 ping6 -I 2001:718:1:e::23:3257 -c 1 2001:718:1:e::1 ifconfig eth0 del 2001:718:1:e::23:3257/64 2001:718:1:e::23:3257 - IPv6 address of VE 2001:718:1:e::1 - gateway That will cause that router will learn about presence of VE. It lasts for several hours. I discovered it at about 17 clock and now at 22 are VE still IPv6 online... but I'm afraid that clearing IPv6 neighbours table on router will kill this. Something is not working on HW node. I'm running 2.6.18-028stab051 on Debian Etch. Output of sysctl -a |grep net.ipv6 | sort /tmp/chlivek.ipv6 is attached. Hope someone will point out where problem is. Yesterday I've reboot my second HW node... -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ net.ipv6.bindv6only = 0 net.ipv6.conf.all.accept_ra = 1 net.ipv6.conf.all.accept_ra_defrtr = 1 net.ipv6.conf.all.accept_ra_pinfo = 1 net.ipv6.conf.all.accept_ra_rtr_pref = 1 net.ipv6.conf.all.accept_redirects = 1 net.ipv6.conf.all.autoconf = 1 net.ipv6.conf.all.dad_transmits = 1 net.ipv6.conf.all.force_mld_version = 0 net.ipv6.conf.all.forwarding = 1 net.ipv6.conf.all.hop_limit = 64 net.ipv6.conf.all.max_addresses = 16 net.ipv6.conf.all.max_desync_factor = 600 net.ipv6.conf.all.mtu = 1280 net.ipv6.conf.all.regen_max_retry = 5 net.ipv6.conf.all.router_probe_interval = 60 net.ipv6.conf.all.router_solicitation_delay = 1 net.ipv6.conf.all.router_solicitation_interval = 4 net.ipv6.conf.all.router_solicitations = 3 net.ipv6.conf.all.temp_prefered_lft = 86400 net.ipv6.conf.all.temp_valid_lft = 604800 net.ipv6.conf.all.use_tempaddr = 0 net.ipv6.conf.default.accept_ra = 1 net.ipv6.conf.default.accept_ra_defrtr = 1 net.ipv6.conf.default.accept_ra_pinfo = 1 net.ipv6.conf.default.accept_ra_rtr_pref = 1 net.ipv6.conf.default.accept_redirects = 1 net.ipv6.conf.default.autoconf = 1 net.ipv6.conf.default.dad_transmits = 1 net.ipv6.conf.default.force_mld_version = 0 net.ipv6.conf.default.forwarding = 1 net.ipv6.conf.default.hop_limit = 64 net.ipv6.conf.default.max_addresses = 16 net.ipv6.conf.default.max_desync_factor = 600 net.ipv6.conf.default.mtu = 1280 net.ipv6.conf.default.regen_max_retry = 5 net.ipv6.conf.default.router_probe_interval = 60 net.ipv6.conf.default.router_solicitation_delay = 1 net.ipv6.conf.default.router_solicitation_interval = 4 net.ipv6.conf.default.router_solicitations = 3 net.ipv6.conf.default.temp_prefered_lft = 86400 net.ipv6.conf.default.temp_valid_lft = 604800 net.ipv6.conf.default.use_tempaddr = 0 net.ipv6.conf.eth0.accept_ra = 1 net.ipv6.conf.eth0.accept_ra_defrtr = 1 net.ipv6.conf.eth0.accept_ra_pinfo = 1 net.ipv6.conf.eth0.accept_ra_rtr_pref = 1 net.ipv6.conf.eth0.accept_redirects = 1 net.ipv6.conf.eth0.autoconf = 0 net.ipv6.conf.eth0.dad_transmits = 1 net.ipv6.conf.eth0.force_mld_version = 0 net.ipv6.conf.eth0.forwarding = 1 net.ipv6.conf.eth0.hop_limit = 64 net.ipv6.conf.eth0.max_addresses = 16 net.ipv6.conf.eth0.max_desync_factor = 600 net.ipv6.conf.eth0.mtu = 1500 net.ipv6.conf.eth0.regen_max_retry = 5 net.ipv6.conf.eth0.router_probe_interval = 60 net.ipv6.conf.eth0.router_solicitation_delay = 1 net.ipv6.conf.eth0.router_solicitation_interval = 4 net.ipv6.conf.eth0.router_solicitations = 3 net.ipv6.conf.eth0.temp_prefered_lft = 86400 net.ipv6.conf.eth0.temp_valid_lft = 604800 net.ipv6.conf.eth0.use_tempaddr = 0 net.ipv6.conf.lo.accept_ra = 1 net.ipv6.conf.lo.accept_ra_defrtr = 1
Re: [Users] IPv6 ??
Hi, Thorsten Schifferdecker wrote: @jan: how get your IPv6 connectivity ? I've static setup on HW node: iface eth0 inet6 static post-up /sbin/sysctl -w net.ipv6.conf.eth0.autoconf=0 post-up /sbin/sysctl -w net.ipv6.conf.all.forwarding=1 address 2001:718:1:e::23:3254 gateway 2001:718:1:e::1 netmask 64 Traceroute from HW node: chlivek:~# traceroute6 2001:838:1:1:210:dcff:fe20:7c7c traceroute to 2001:838:1:1:210:dcff:fe20:7c7c (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:718:1:e::23:3254, 30 hops max, 16 byte packets 1 2001:718:1:e::1 (2001:718:1:e::1) 0.983 ms 4.869 ms 2.949 ms 2 2001:718:0:607::1 (2001:718:0:607::1) 4.943 ms 4.823 ms 2.895 ms 3 2001:718:0:607::2 (2001:718:0:607::2) 4.929 ms 4.867 ms 2.968 ms 4 ipv6-ge-2-1-0.prg11.ip.tiscali.net (2001:7f8:14::3:1) 3.359 ms 3.328 ms 4.439 ms 5 so-5-1-0.fra40.ip6.tiscali.net (2001:668:0:2::1:291) 9.113 ms 8.861 ms 14.915 ms 6 so-4-1-0.dus11.ip6.tiscali.net (2001:668:0:2::1:402) 12.322 ms 12.146 ms 15.893 ms 7 so-7-0-0.ams22.ip6.tiscali.net (2001:668:0:2::1:482) 15.88 ms 16.848 ms 15.919 ms 8 so-6-0-0.ams11.ip6.tiscali.net (2001:668:0:2::1:271) 15.889 ms 15.955 ms 14.971 ms 9 ge6-2-0.br0.ams3.nl.gbxs.net (2001:7f8:1::a500:9009:1) 15.511 ms 15.454 ms 15.972 ms 10 ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 15.437 ms 15.937 ms 15.837 ms 11 2001:838:0:14::2 (2001:838:0:14::2) 16.108 ms 15.294 ms 16.615 ms 12 2001:838:0:10::2 (2001:838:0:10::2) 21.508 ms 21.488 ms 17.428 ms 13 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 21.508 ms 21.46 ms 18.441 ms From VE (differnet IP, that 3257 was just experiemnt with my trick). [EMAIL PROTECTED]:~# traceroute6 2001:838:1:1:210:dcff:fe20:7c7c traceroute to 2001:838:1:1:210:dcff:fe20:7c7c (2001:838:1:1:210:dcff:fe20:7c7c) from 2001:718:1:e::23:3248, 30 hops max, 16 byte packets 1 2001:718:1:e::23:3254 (2001:718:1:e::23:3254) 0.045 ms 0.015 ms 0.011 ms 2 2001:718:0:607::1 (2001:718:0:607::1) 1.105 ms 0.837 ms 1.381 ms 3 2001:718:0:607::2 (2001:718:0:607::2) 0.663 ms 0.44 ms 0.373 ms 4 ipv6-ge-2-1-0.prg11.ip.tiscali.net (2001:7f8:14::3:1) 0.566 ms 0.529 ms 0.529 ms 5 so-5-1-0.fra40.ip6.tiscali.net (2001:668:0:2::1:291) 8.551 ms 8.493 ms 8.499 ms 6 so-4-1-0.dus11.ip6.tiscali.net (2001:668:0:2::1:402) 11.302 ms 11.26 ms 11.256 ms 7 so-0-0-0.ams22.ip6.tiscali.net (2001:668:0:2::1:122) 15.086 ms 15.044 ms 15.039 ms 8 pos-7-5-0.ams11.ip6.tiscali.net (2001:668:0:2::630) 14.943 ms 14.945 ms 15.464 ms 9 ge6-2-0.br0.ams3.nl.gbxs.net (2001:7f8:1::a500:9009:1) 15.65 ms 15.52 ms 16.392 ms 10 ams-ix2.ipv6.concepts.nl (2001:7f8:1::a501:2871:2) 17.111 ms 15.812 ms 15.879 ms 11 2001:838:0:14::2 (2001:838:0:14::2) 16.031 ms 15.915 ms 15.91 ms 12 2001:838:0:10::2 (2001:838:0:10::2) 17.83 ms 18.28 ms 17.903 ms 13 noc.sixxs.net (2001:838:1:1:210:dcff:fe20:7c7c) 17.661 ms 18.263 ms 17.993 ms Could you please try traceroute at 2001:718:1:e::23:3254? Path seams to be different from yours. But I'm not sure if that could indicate something bad in your IPv6 network setup. I'm not able to reach machines which are in our own network so it looks like something more fundamental. For IPv4 I will say that arp is not working but ... -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ signature.asc Description: OpenPGP digital signature ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 with venet
Vitaliy Gusev wrote: Please check /proc/sys/net/ipv6/conf/all/forwarding It is disabled: staj-dev:~# for f in /proc/sys/net/ipv6/conf/*/forwarding; do echo $f; cat $f; done /proc/sys/net/ipv6/conf/all/forwarding 0 /proc/sys/net/ipv6/conf/default/forwarding 0 /proc/sys/net/ipv6/conf/eth0/forwarding 0 /proc/sys/net/ipv6/conf/lo/forwarding 0 /proc/sys/net/ipv6/conf/venet0/forwarding 0 Problem is that when I do: echo 1 /proc/sys/net/ipv6/conf/all/forwarding HW node stops responding on IPv6 ping, reason probably is that setting that removes default GW: staj-dev:~# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 13 1 lo 2001:718:1:e::/128 :: U 0 02 lo 2001:718:1:e::23:3004/128 :: U 0 266 1 lo 2001:718:1:e::/64 :: U 256217 0 eth0 fe80::/128 :: U 0 02 lo fe80::1/128 :: U 0 01 lo fe80::213:72ff:fe1b:b97/128 :: U 0 81 lo fe80::/64 :: U 25600 eth0 fe80::/64 :: U 25600 venet0 ff02::1/128 ff02::1 UC0 229 0 eth0 ff00::/8:: U 25600 eth0 ff00::/8:: U 25600 venet0 When I set GW manualy it start work and it works also for VE. GREAT! Well and now. Why setting forwarding=1 removes GW? Is there any way how to add it there automaticaly without my attention? I'm afraid that GW IP fe80::215:faff:fe87:3100 is somehow related to router MAC and that it will change when router become replaced. Any sugestion on this? Thanks a lot! -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 with venet
Hi Jan, Jan Tomasek schrieb: Vitaliy Gusev wrote: Please check /proc/sys/net/ipv6/conf/all/forwarding [...] Problem is that when I do: echo 1 /proc/sys/net/ipv6/conf/all/forwarding HW node stops responding on IPv6 ping, reason probably is that setting that removes default GW: Router Advertisements (=autoconfiguration) are ignored on setting forward to 1 to IPv6 proc settings and your (automatic) default route ( ::0 ), is set to a RA IPv6 (link-local) address, is gone. for Debian you can set IPv6 (addy and route) on your VE0 (hardware node): --8--( /etc/network/interfaces )-- [...] iface DEVICE [...] iface DEVICE inet6 static address IPv6_ADDRESS netmask NETMASK gateway IPv6_ADDRESS_of_your_GATEWAY # set IPv6 forwarding here or in /etc/sysctl.conf # read man page of interfaces (5) [...] --8-- Regards, Thorsten Schifferdecker ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 with venet
Hi, after upgrade to vzctl version 3.0.18-1dso1 I got new set of /etc/vz/dists/scripts/. There were changes in IPv6 code for Debian. Thanks to those changes now IPv6 works between HW node and VE: staj-dev:~# ping6 2001:718:1:e::23:3005 PING 2001:718:1:e::23:3005(2001:718:1:e::23:3005) 56 data bytes 64 bytes from 2001:718:1:e::23:3005: icmp_seq=1 ttl=64 time=0.068 ms Problem is that I still can not reach VE from outside (staff is box with IPv6 support). [EMAIL PROTECTED]:~$ ping6 2001:718:1:e::23:3005 PING 2001:718:1:e::23:3005(2001:718:1:e::23:3005) 56 data bytes ping does not show anything, it just hangs. In tcpdump on HW node I see: 15:38:41.465836 802.1d unknown version 15:38:41.498548 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 923, length 64 15:38:42.498349 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 924, length 64 15:38:43.462572 802.1d unknown version 15:38:43.498152 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 925, length 64 15:38:43.733136 arp who-has 195.113.233.73 tell 195.113.233.1 15:38:44.497951 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 926, length 64 15:38:45.427653 IP6 fe80::215:faff:fe87:3100 ip6-allnodes: ICMP6, router advertisement, length 64 15:38:45.462453 802.1d unknown version 15:38:45.497753 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 927, length 64 15:38:46.497552 IP6 staff.cesnet.cz 2001:718:1:e::23:3005: ICMP6, echo request, seq 928, length 64 I was suspecting route problems but routes does look ok. VE: [EMAIL PROTECTED]:/# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 11 lo ::1/128 :: U 0 01 lo 2001:718:1:e::23:3005/128 :: U 0 13 1 lo 2001:718:1:101:20b:dbff:fe93:5c38/128 2001:718:1:101:20b:dbff:fe93:5c38 UC0 101 0 venet0 fe80::/64 :: U 25600 venet0 ff00::/8:: U 25600 venet0 ::/0:: U 25600 venet0 HW node: staj-dev:/proc/sys/net/ipv6/conf/venet0# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 81 lo 2001:718:1:e::23:3004/128 :: U 0 926 1 lo 2001:718:1:e::23:3005/128 :: U 1024 00 venet0 2001:718:1:e:213:72ff:fe1b:b97/128 :: U 0 01 lo 2001:718:1:e::/64 :: U 256302 0 eth0 fe80::1/128 :: U 0 01 lo fe80::213:72ff:fe1b:b97/128 :: U 0 58 1 lo fe80::/64 :: U 25600 eth0 fe80::/64 :: U 25600 venet0 ff02::1/128 ff02::1 UC0 327 0 eth0 ff00::/8:: U 25600 eth0 ff00::/8:: U 25600 venet0 ::/0fe80::215:faff:fe87:3100UGDA 1024 483 0 eth0 Please, does anyone have any sugestions? -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 again but this time with veth
venet device works with IPv6! Describe steps which you did for venet device. On the Thursday 28 June 2007 22:44 Jan Tomasek, wrote: I need IPv4 and IPv6 support in VE. I would prefer venet interface, but that doesn't work. See thread: http://forum.openvz.org/index.php?t=msggoto=12809srch=IPv6#msg_12809 Do you have any other suggestions? -- Vitaliy Gusev, ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 again but this time with veth
You added veth012.0 device to the bridge br0. How about eth0 ? On the Friday 29 June 2007 12:23 Jan Tomasek, wrote: Oh. I got lost! Could I try to describe it again? My HW node is staj-dev: auto eth0 iface eth0 inet static address 195.113.233.4 netmask 255.255.255.0 network 195.113.233.0 broadcast 195.113.233.255 gateway 195.113.233.1 dns-nameservers 195.113.144.233 195.113.144.194 dns-search cesnet.cz iface eth0 inet6 static post-up /sbin/sysctl -w net.ipv6.conf.eth0.autoconf=0 address 2001:718:1:e::23:3004 netmask 64 My VE node, has this config (ip6v2-test): auto eth0 iface eth0 inet static address 195.113.233.12 netmask 255.255.255.0 network 195.113.233.0 broadcast 195.113.233.255 gateway 195.113.233.4 dns-nameservers 195.113.144.233 195.113.144.194 dns-search cesnet.cz eth0 inet6 static iface eth0 inet6 static address 2001:718:1:e::23:3012 netmask 64 After executing: brctl addbr vzbr0 brctl addif vzbr0 veth012.0 ifconfig vzbr0 0 echo 1 /proc/sys/net/ipv4/conf/vzbr0/forwarding echo 1 /proc/sys/net/ipv4/conf/vzbr0/proxy_arp echo 1 /proc/sys/net/ipv4/conf/eth0/forwarding echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp ip route add 195.113.233.12 dev vzbr0 ip route add 2001:718:1:e::23:3012 dev vzbr0 **MARK** VE starts to be reachable from Internet on IPv4. What should I do next? echo 1 /proc/sys/net/ipv6/conf/eth0/forwarding somehow broke IPv6 for HW node. echo 1 /proc/sys/net/ipv6/conf/vzbr0/forwarding cause no problem. Well - returning to point marked as **MARK**. Route table on HW node: staj-dev:~# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 61 lo 2001:718:1:e::23:3004/128 :: U 0 788 1 lo 2001:718:1:e::23:3012/128 :: U 1024 00 vzbr0 2001:718:1:e::/64 :: U 256169 0 eth0 fe80::/128 :: U 0 02 lo fe80::1/128 :: U 0 01 lo fe80::20c:29ff:fe63:a674/128:: U 0 01 lo fe80::20c:29ff:fe63:a674/128:: U 0 01 lo fe80::213:72ff:fe1b:b97/128 :: U 0 32 1 lo fe80::/64 :: U 25600 eth0 fe80::/64 :: U 25600 venet0 fe80::/64 :: U 25600 veth012.0 fe80::/64 :: U 25600 vzbr0 f020::1/128 ff02::1 UC0 165 0 eth0 ff00::/8:: U 25600 eth0 ff00::/8:: U 25600 venet0 ff00::/8:: U 25600 veth012.0 ff00::/8:: U 25600 vzbr0 ::/0fe80::215:faff:fe87:3100 UGDA 1024 167 0 eth0 Route table on VE node: [EMAIL PROTECTED]:/# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 11 lo 2001:718:1:e::23:3012/128 :: U 0 53 1 lo 2001:718:1:e::/64 :: U 25600 eth0 fe80::20c:29ff:fe63:a673/128:: U 0 01 lo fe80::/64
Re: [Users] IPv6 again but this time with veth
Possible it is a bug in vzctl's configuration script. Which OS do you use for VE/Host? What is vzctl version? On the Friday 29 June 2007 12:53 Jan Tomasek, wrote: Vitaliy Gusev wrote: venet device works with IPv6! Describe steps which you did for venet device. I created VE 233005: IPv4=195.113.233.5 IPv6=2001:718:1:e::23:3005 IPv4 is working ok. When I try to add IPv6 I get: staj-dev:~# vzctl set 233005 --ipadd '2001:718:1:e::23:3005' --save Adding IP address(es): 2001:718:1:e::23:3005 Failed to bring up venet0:1. Configure meminfo: 49152 Saved parameters for VE 233005 staj-dev:~# vzctl enter 233005 entered into VE 233005 [EMAIL PROTECTED]:/# ifconfig -a loLink 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: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) venet0Link 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 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 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) venet0:0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:195.113.233.5 P-t-P:195.113.233.5 Bcast:0.0.0.0 Mask:255.255.255.255 UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1 There is no venet0:1 inside of VE 233005. -- Vitaliy Gusev, ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 again but this time with veth
Vitaliy Gusev wrote: Possible it is a bug in vzctl's configuration script. Which OS do you use for VE/Host? What is vzctl version? Both systems are Debian etch. staj-dev:~# vzctl --version vzctl version 3.0.16-5dso1 -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 again but this time with veth
Vitaliy Gusev wrote: You added veth012.0 device to the bridge br0. How about eth0 ? It wasn't there. After adding it I finally could yell IT WORSK! but just for while. :( In few minutes it stopped working on IPv4 (v6 is still fine). I discovered that problem is in arp (my GW is .233.1): staj-dev:~# arp -n Address HWtype HWaddress Flags MaskIface 195.113.233.224 (incomplete) eth0 195.113.233.12 ether 00:0C:29:63:A6:73 C vzbr0 195.113.233.254 (incomplete) eth0 195.113.233.92 (incomplete) eth0 195.113.233.193 (incomplete) eth0 195.113.233.99 ether 00:0C:29:6D:67:1A C vzbr0 195.113.233.99 (incomplete) eth0 195.113.233.36 (incomplete) eth0 195.113.233.254 ether 00:13:72:39:61:AA C vzbr0 195.113.233.2(incomplete) eth0 195.113.233.1(incomplete) eth0 195.113.233.245 (incomplete) eth0 195.113.233.246 (incomplete) eth0 staj-dev:~# arp -s 195.113.233.1 00:15:FA:87:31:0 Address HWtype HWaddress Flags MaskIface 195.113.233.91 (incomplete) eth0 195.113.233.246 (incomplete) eth0 195.113.233.34 (incomplete) eth0 195.113.233.12 ether 00:0C:29:63:A6:73 C vzbr0 195.113.233.74 (incomplete) eth0 195.113.233.1ether 00:15:FA:87:31:00 CMeth0 fixes problem. But that is really ugly hack, this way I have to add static arp records for every host in network 195.113.233.0/24 outside of this HW node. That is not good way. Any idea why ARP (and IPv4) stop work? Command I do execute are: brctl addbr vzbr0 ifconfig vzbr0 0 echo 1 /proc/sys/net/ipv4/conf/vzbr0/forwarding echo 1 /proc/sys/net/ipv4/conf/vzbr0/proxy_arp brctl addif vzbr0 veth012.0 brctl addif vzbr0 eth0 ip route add 195.113.233.12 dev vzbr0 -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 again but this time with veth
Vitaliy Gusev wrote: Hello, do you use a bridge? Probably not... if there is some place where I should RTFM, than just provide me URL please ;) I was hoping setup will be similar as is for IPv4. IPv6 itself is new for me, and with combination with OpenVZ quite hard to understand How I see staj-dev is a host-node, Yes. but what is two others hosts semik, that is just IPv4 capable box, used for demonstration that my veth012.0 interface is at least able to communicate on IPv4. ip6v2-test? That is VE 233012 where I'm trying to get IPv6 working. What steps did you do for veth012.0 ? staj-dev# vzctl set 233012 --netif_add eth0,00:0C:29:63:A6:73,veth012.0,00:0C:29:63:A6:74 --save staj-dev:~# ifconfig veth012.0 0 staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/veth012.0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/veth012.0/proxy_arp staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/eth0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp staj-dev:~# ip route add 195.113.233.012 dev veth012.0 staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/veth012.0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/eth0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/all/forwarding Am I now more clear? Thanks for help. -- --- Jan Tomasek aka Semik http://www.tomasek.cz/ ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
[Users] IPv6 again but this time with veth
Hello, few weeks ago I was trying to setup IPv6, but that doesn't work. http://forum.openvz.org/index.php?t=msggoto=12809srch=IPv6#msg_12809 I would really like to have this feature. So I'm trying to experiment with veth devices, but not much success again :( My host node has IPv6 support: staj-dev:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:13:72:1B:0B:97 inet addr:195.113.233.4 Bcast:195.113.233.255 Mask:255.255.255.0 inet6 addr: 2001:718:1:e::23:3004/64 Scope:Global inet6 addr: fe80::213:72ff:fe1b:b97/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:2136 errors:0 dropped:0 overruns:0 frame:0 TX packets:1304 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:211656 (206.6 KiB) TX bytes:138480 (135.2 KiB) Interrupt:17 It is accessible on IPv6: [EMAIL PROTECTED]:~$ ping6 -c1 2001:718:1:e::23:3004 PING 2001:718:1:e::23:3004(2001:718:1:e::23:3004) 56 data bytes 64 bytes from 2001:718:1:e::23:3004: icmp_seq=0 ttl=63 time=0.129 ms I setup IPv4 part this way: staj-dev:~# ifconfig veth012.0 0 staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/veth012.0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/veth012.0/proxy_arp staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/eth0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv4/conf/eth0/proxy_arp staj-dev:~# ip route add 195.113.233.012 dev veth012.0 and it works: semik:~$ping -c1 195.113.233.12 PING 195.113.233.12 (195.113.233.12): 56 data bytes 64 bytes from 195.113.233.12: icmp_seq=0 ttl=61 time=0.252 ms I'm trying to follow http://wiki.openvz.org/Virtual_Ethernet_device#Virtual_ethernet_device_with_IPv6 but after executing (2nd, 3rd) lines staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/veth012.0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/eth0/forwarding staj-dev:~# echo 1 /proc/sys/net/ipv6/conf/all/forwarding host node stop responding to ping6. I'm stuck here... I also do not want run router advertisement daemon (if that is possible). My VE should have address 2001:718:1:e::23:3012. Inside VE I setup: [EMAIL PROTECTED]:~# ifconfig eth0 Link encap:Ethernet HWaddr 00:0C:29:63:A6:73 inet addr:195.113.233.12 Bcast:195.113.233.255 Mask:255.255.255.0 inet6 addr: 2001:718:1:e::23:3012/64 Scope:Global inet6 addr: fe80::20c:29ff:fe63:a673/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:88 errors:0 dropped:0 overruns:0 frame:0 TX packets:88 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:7012 (6.8 KiB) TX bytes:6948 (6.7 KiB) [EMAIL PROTECTED]:~# cat /etc/network/interfaces auto lo iface lo inet loopback auto eth0 iface eth0 inet static address 195.113.233.12 netmask 255.255.255.0 network 195.113.233.0 broadcast 195.113.233.255 gateway 195.113.233.4 dns-nameservers 195.113.144.233 195.113.144.194 dns-search cesnet.cz eth0 inet6 static iface eth0 inet6 static address 2001:718:1:e::23:3012 netmask 64 veth interface is configured this way: NETIF=ifname=eth0,mac=00:0C:29:63:A6:73,host_ifname=veth012.0,host_mac=00:0C:29:63:A6:74 inside VE I see reasonable routes: [EMAIL PROTECTED]:~# route -6 Kernel IPv6 routing table Destination Next Hop Flags Metric RefUse Iface ::1/128 :: U 0 11 lo 2001:718:1:e::23:3004/128 2001:718:1:e::23:3004 UC0 49 0 eth0 2001:718:1:e::23:3012/128 :: U 0 142 1 lo 2001:718:1:e::/64 :: U 25600 eth0 fe80::20c:29ff:fe63:a673/128:: U 0 01 lo fe80::/64 :: U 25600 eth0 ff02::16/128ff02::16UC0 50 eth0 ff00::/8:: U 25600 eth0 but I'm not able even to ping to my host: [EMAIL PROTECTED]:~# ping6 2001:718:1:e::23:3004 PING 2001:718:1:e::23:3004(2001:718:1:e::23:3004) 56 data bytes From 2001:718:1:e::23:3012 icmp_seq=1 Destination unreachable: Address unreachable it is very interesting, that host node see my ping requests: staj-dev:~# tcpdump -i veth012.0 tcpdump: WARNING: veth012.0: no IPv4 address assigned tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on
Re: [Users] IPv6 support in VE
Hi, adding is ok, but when i want delete a IPv6 with --ipdel, it shows: # vzctl set VEID --ipdel fc00::1 [--save] Warning: ipv6 support disabled ---* Deleting IP address(es): Configure meminfo: 49152 Saved parameters for VE VEID Regards, Thorsten Jan, With venet, you use the same ipadd command, for example: vzctl set VEID --ipadd fc00::01 --save Before that, make sure that * your kernel is compiled with IPv6 * ipv6 module is loaded (if IPv6 is compiled as a module) * IPV6 set to yes in /etc/vz/vz.conf Kirill Korotaev wrote: Jan, venet supports IPv6 addresses as well. it's just an article concerning veth only :) Thanks, Kirill Jan Tomasek wrote: Hello, what is state of IPv6 support inside VE? I found: http://wiki.openvz.org/Virtual_Ethernet_device#Virtual_ethernet_device_with_IPv6 but that looks quite complicated comparing to IPv4 where I just need to use `vzctl --ipadd 1.2.3.4` and that is all. Do I have to go with veth or is there chance how to configure IPv6 on venet? Thanks for sugestions ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
Re: [Users] IPv6 support in VE
Jan, With venet, you use the same ipadd command, for example: vzctl set VEID --ipadd fc00::01 --save Before that, make sure that * your kernel is compiled with IPv6 * ipv6 module is loaded (if IPv6 is compiled as a module) * IPV6 set to yes in /etc/vz/vz.conf Kirill Korotaev wrote: Jan, venet supports IPv6 addresses as well. it's just an article concerning veth only :) Thanks, Kirill Jan Tomasek wrote: Hello, what is state of IPv6 support inside VE? I found: http://wiki.openvz.org/Virtual_Ethernet_device#Virtual_ethernet_device_with_IPv6 but that looks quite complicated comparing to IPv4 where I just need to use `vzctl --ipadd 1.2.3.4` and that is all. Do I have to go with veth or is there chance how to configure IPv6 on venet? Thanks for sugestions ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users ___ Users mailing list Users@openvz.org https://openvz.org/mailman/listinfo/users
