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
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
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
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:
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
>
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
(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
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
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
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
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
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
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
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 -
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,
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 -
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
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
-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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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
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:
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
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:
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
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:
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/
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):
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
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:
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
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,
53 matches
Mail list logo
