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
