Please help: OVH + Proxmox + LXC => IPv6 not working

haru

Hi all,

First post here, i'm facing odd issues with my servers. I installed proxmox zfs 4.4 template from OVH, download LXC centos7 template for proxmox and create LXCs via GUI. Ipv4 work well on all servers, but i have only one server that have IPv6 work inside LXC. I tried many tutorials from internet but still no luck, so please guide me if you have time, thank you very much

HOST: IPv6 Work fine

1. nano /etc/network/interfaces
   auto lo iface lo inet loopback auto vmbr1 iface vmbr1 inet manual post-up /etc/pve/kvm-networking.sh bridge_ports dummy0 bridge_stp off bridge_fd 0 auto vmbr0 iface vmbr0 inet static address 217.182.193.xxx netmask 255.255.255.0 network 217.182.193.0 broadcast 217.182.193.255 gateway 217.182.193.254 bridge_ports eth0 bridge_stp off bridge_fd 0 iface vmbr0 inet6 static address 2001:41d0:0303:1cxx:: netmask 64 post-up /sbin/ip -f inet6 route add 2001:41d0:0303:1cff:ff:ff:ff:ff dev vmbr0 post-up /sbin/ip -f inet6 route add default via 2001:41d0:0303:1cff:ff:ff:ff:ff pre-down /sbin/ip -f inet6 route del default via 2001:41d0:0303:1cff:ff:ff:ff:ff pre-down /sbin/ip -f inet6 route del 2001:41d0:0303:1cff:ff:ff:ff:ff dev vmbr0

2. Ping Ipv6 of LXC: work
   PING 2001:41d0:303:1cxx::1(2001:41d0:303:1cxx::1) 56 data bytes 64 bytes from 2001:41d0:303:1cxx::1: icmp_seq=1 ttl=64 time=0.037 ms 64 bytes from 2001:41d0:303:1cxx::1: icmp_seq=2 ttl=64 time=0.051 ms

3. ping6 -I vmbr0 ff02::2 => Work
   PING ff02::2(ff02::2) from fe80::a6bf:1ff:fe17:cbb4 vmbr0: 56 data bytes 64 bytes from fe80::2d7:8fff:fea8:f841: icmp_seq=1 ttl=64 time=0.690 ms 64 bytes from fe80::2d7:8fff:fea8:f541: icmp_seq=1 ttl=64 time=1.16 ms (DUP!) 64 bytes from fe80::2d7:8fff:fea8:f841: icmp_seq=2 ttl=64 time=0.711 ms 64 bytes from fe80::2d7:8fff:fea8:f541: icmp_seq=2 ttl=64 time=0.724 ms (DUP!)

4. ip -6 a
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 4: vmbr1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UNKNOWN qlen 1000 inet6 fe80::6021:4dff:feed:f794/64 scope link valid_lft forever preferred_lft forever 17: vmbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 2001:41d0:303:1cxx::/64 scope global valid_lft forever preferred_lft forever inet6 fe80::a6bf:1ff:fe17:cbb4/64 scope link valid_lft forever preferred_lft forever

5. ip -6 r
   2001:41d0:303:1cxx::/64 dev vmbr0 proto kernel metric 256 pref medium 2001:41d0:303:1cff:ff:ff:ff:ff dev vmbr0 metric 1024 pref medium fe80::/64 dev vmbr1 proto kernel metric 256 pref medium fe80::/64 dev vmbr0 proto kernel metric 256 pref medium default via 2001:41d0:303:1cff:ff:ff:ff:ff dev vmbr0 metric 1024 pref medium

LXC: IPv4 work, IPv6 not

1. Ping gateway work:
   PING 2001:41d0:303:1cff:ff:ff:ff:ff(2001:41d0:303:1cff:ff:ff:ff:ff) 56 data bytes 64 bytes from 2001:41d0:303:1cff:ff:ff:ff:ff: icmp_seq=1 ttl=64 time=0.728 ms 64 bytes from 2001:41d0:303:1cff:ff:ff:ff:ff: icmp_seq=2 ttl=64 time=0.736 ms

2. Ping HOST's IPv6 work:
   PING 2001:41d0:303:1cxx::(2001:41d0:303:1cxx::) 56 data bytes 64 bytes from 2001:41d0:303:1cxx::: icmp_seq=1 ttl=64 time=0.025 ms 64 bytes from 2001:41d0:303:1cxx::: icmp_seq=2 ttl=64 time=0.042 ms

3. Ping Google not work:
   PING google.com(par21s11-in-x0e.1e100.net (2a00:1450:4007:80c::200e)) 56 data bytes ^C --- google.com ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 29999ms

4. ip -6 a
   1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1 inet6 ::1/128 scope host valid_lft forever preferred_lft forever 18: eth0@if19: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000 inet6 2001:41d0:303:1cxx::1/64 scope global valid_lft forever preferred_lft forever inet6 fe80::ff:fea9:b407/64 scope link valid_lft forever preferred_lft forever

5. ip -6 r
   unreachable ::/96 dev lo metric 1024 error -113 unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -113 2001:41d0:303:1cxx::/64 dev eth0 proto kernel metric 256 2001:41d0:303:1cff:ff:ff:ff:ff dev eth0 metric 1024 unreachable 2002:a00::/24 dev lo metric 1024 error -113 unreachable 2002:7f00::/24 dev lo metric 1024 error -113 unreachable 2002:a9fe::/32 dev lo metric 1024 error -113 unreachable 2002:ac10::/28 dev lo metric 1024 error -113 unreachable 2002:c0a8::/32 dev lo metric 1024 error -113 unreachable 2002:e000::/19 dev lo metric 1024 error -113 unreachable 3ffe:ffff::/32 dev lo metric 1024 error -113 fe80::/64 dev eth0 proto kernel metric 256 default via 2001:41d0:303:1cff:ff:ff:ff:ff dev eth0 metric 1024

6. cat /etc/sysconfig/network-scripts/ifcfg-eth0
   ...... IPV6INIT=yes IPV6_AUTOCONF=no IPV6ADDR=2001:41d0:303:1cxx::1/64

7. cat /etc/sysconfig/network-scripts/route6-eth0
   \# --- BEGIN PVE --- 2001:41d0:303:1cff:ff:ff:ff:ff dev eth0 default via 2001:41d0:303:1cff:ff:ff:ff:ff dev eth0 \# --- END PVE ---

jaypeesmith

I have the same setup (except mine are KVM) and couldn't get IPv6 on my VMs to ping the outside world. For me, it was an issue on the host node's /etc/sysctl.conf file.

On the host node, here are the lines I needed in /etc/sysctl.conf to get it working:

# Disable IPv6 autoconf 
net.ipv6.conf.all.autoconf = 0  
net.ipv6.conf.default.autoconf = 0  
net.ipv6.conf.vmbr0.autoconf = 0  
net.ipv6.conf.all.accept_ra = 0  
net.ipv6.conf.default.accept_ra = 0   
net.ipv6.conf.vmbr0.accept_ra = 0  
net.ipv6.conf.vmbr0.accept_ra = 0  
net.ipv6.conf.vmbr0.autoconf = 0  

#the previous lines were already there. These are what I added.  
net.ipv6.conf.default.proxy_ndp=1  
net.ipv6.conf.all.proxy_ndp=1  
net.ipv6.conf.default.forwarding=1  
net.ipv6.conf.all.forwarding = 1 

After these were added, I ran sysctl -p from the command line for the change to take effect.

I can't guarantee this is the problem you're having but, it looks similar to what I experienced.

ljseals

I have a similar problem here https://www.lowendtalk.com/discussion/112473/does-anyone-have-a-working-tutorial-in-order-to-get-proxmox-to-work-with-kimsufi-using-ipv6#latest but honestly gave up on it.

http://www.microsofttranslator.com/bv.aspx?from=&to=en&a=http://sngr.org/2017/02/单ipv4服务器建纯ipv6的vps用于web管理pt挂机.html

http://wiki.x8e.net/doku.php?id=proxmox_ipv6

Are decent tutorials but I guess there is something about ipv6 I just do not understand as I could not ssh in the vm from the ipv4 address nor could I connect it out but I was able to get internet inside of the VM. One other thing is that I could not get github to download apps I guess they do not allow IPV6. I honestly do not know so if you find it out post a complete tutorial from beginning to end for newbs.... Those slightly below the explorer level. God bless you!

Also I could ping these in the VM using these tutorials.

Test IPv6 is working

ping6 -c 8 ::

Test IPv6 has connection to internet

ping6 -c 8 2001:4860:4860::8888

Test IPv6 DNS is working

ping6 -c 8 ipv6.google.com

https://forum.online.net/index.php?/topic/5380-configuring-ipv6-in-proxmox-on-dedibox-from-onlinenet/

Is also something that I used.

haru

@jaypeesmith said:
I have the same setup (except mine are KVM) and couldn't get IPv6 on my VMs to ping the outside world. For me, it was an issue on the host node's /etc/sysctl.conf file.

On the host node, here are the lines I needed in /etc/sysctl.conf to get it working:

# Disable IPv6 autoconf
net.ipv6.conf.all.autoconf = 0
net.ipv6.conf.default.autoconf = 0
net.ipv6.conf.vmbr0.autoconf = 0
net.ipv6.conf.all.accept_ra = 0
net.ipv6.conf.default.accept_ra = 0
net.ipv6.conf.vmbr0.accept_ra = 0
net.ipv6.conf.vmbr0.accept_ra = 0
net.ipv6.conf.vmbr0.autoconf = 0

#the previous lines were already there. These are what I added.
net.ipv6.conf.default.proxy_ndp=1
net.ipv6.conf.all.proxy_ndp=1
net.ipv6.conf.default.forwarding=1
net.ipv6.conf.all.forwarding = 1

After these were added, I ran sysctl -p from the command line for the change to take effect.

I can't guarantee this is the problem you're having but, it looks similar to what I experienced.

Work for me too, thank you very much

@ljseals did you try jaypeesmith's solution above? it may work for you too

ljseals

I will try again @haru what tutorial did you use?

haru

@ljseals said:
I will try again @haru what tutorial did you use?

Just add follow lines at the end of /etc/sysctl.conf

net.ipv6.conf.default.proxy_ndp=1 net.ipv6.conf.all.proxy_ndp=1 net.ipv6.conf.default.forwarding=1 net.ipv6.conf.all.forwarding = 1

ljseals

@ljseals said: One other thing is that I could not get github to download apps I guess they do not allow IPV6.

Is seems that you need a Nat gateway http://aa.net.uk/kb-broadband-ipv6-nat64.html in order to download from github.

@FVPS said:
No, they don't really have IPv6. So it's a bit of a pain to work on IPv6 only VPSs because so many sites don't have IPv6.

I used DNS64/NAT64 nameservers to access IPv4 only sites on a IPv6 only service.

http://aa.net.uk/kb-broadband-ipv6-nat64.html



Just add

> nameserver 2001:8b0:6464::1
> nameserver 2001:8b0:6464::2
> 

To the top of your resolv.conf



And then wget and et cetera will be able to grab content from IPv4 only sources over address translation through these DNS servers. Speed is alright actually if not even sometimes really decent!

Hope this can help you to get over the fact that something as big and as popular as GitHub has no IPv6.