Hi everyone,
Im having a strange issue with lxc containers and ipv6.
I set on every machine fe80::1 as ipv6 gateway. When using kvm, it comes up at boot it can ping externally any unicast ipv6 in the world, but when doing exactly the same in LXC, it takes time to start pinging (between 120 and 240 seconds, put any number in between those are limits), then it can start pinging.
# ping google.com
PING google.com(mad07s09-in-x0e.1e100.net (2a00:1450:4003:802::200e)) 56 data bytes
--- google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 27ms
# ip -6 neigh
fe80::1 dev eth0 FAILED
Two minutes later:
# ping google.com
PING google.com(mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e)) 56 data bytes
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=1 ttl=120 time=0.889 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=2 ttl=120 time=0.861 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=3 ttl=120 time=0.891 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=4 ttl=120 time=0.845 ms
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 39ms
rtt min/avg/max/mdev = 0.845/0.871/0.891/0.035 ms
# ip -6 neigh
fe80::1 dev eth0 lladdr 00:XX:XX:XX:00:23 router DELAY
The HV is configured with OVS OVSBridge on vmbr0. Every machine has a vlan tag for the network they should have access.
Any help would be very much appreciated.
PVE version (Yes i must update it):
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1
Im having a strange issue with lxc containers and ipv6.
I set on every machine fe80::1 as ipv6 gateway. When using kvm, it comes up at boot it can ping externally any unicast ipv6 in the world, but when doing exactly the same in LXC, it takes time to start pinging (between 120 and 240 seconds, put any number in between those are limits), then it can start pinging.
# ping google.com
PING google.com(mad07s09-in-x0e.1e100.net (2a00:1450:4003:802::200e)) 56 data bytes
--- google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 27ms
# ip -6 neigh
fe80::1 dev eth0 FAILED
Two minutes later:
# ping google.com
PING google.com(mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e)) 56 data bytes
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=1 ttl=120 time=0.889 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=2 ttl=120 time=0.861 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=3 ttl=120 time=0.891 ms
64 bytes from mad06s09-in-x0e.1e100.net (2a00:1450:4003:807::200e): icmp_seq=4 ttl=120 time=0.845 ms
--- google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 39ms
rtt min/avg/max/mdev = 0.845/0.871/0.891/0.035 ms
# ip -6 neigh
fe80::1 dev eth0 lladdr 00:XX:XX:XX:00:23 router DELAY
The HV is configured with OVS OVSBridge on vmbr0. Every machine has a vlan tag for the network they should have access.
Any help would be very much appreciated.
PVE version (Yes i must update it):
proxmox-ve: 6.3-1 (running kernel: 5.4.78-2-pve)
pve-manager: 6.3-3 (running version: 6.3-3/eee5f901)
pve-kernel-5.4: 6.3-3
pve-kernel-helper: 6.3-3
pve-kernel-5.4.78-2-pve: 5.4.78-2
pve-kernel-5.4.73-1-pve: 5.4.73-1