[Sebastian]

Progress !!

IPv6 addresses have started appearing in the OVH control panel for my servers in Strasbourg SBG1, though no sign yet for Gravelines GRA1.

Once you have been assigned your IPv6 address for a given server, apply the following steps to bring it to life:

1. establish your IPv6 default gateway link-local address

find the MAC address of your default g/w and calculate its link-local address (see EUI-64 Bit Address). e.g.
bash# ip neigh
51.254.112.1 dev eth0 lladdr 82:14:74:20:38:ab REACHABLE
bash#

Transform the MAC address into a link-local address (remembering to flip the 7th bit from the left).
82:14:74:20:38:ab => fe80::8014:74ff:fe20:38ab

Confirm your transformation (remember to suffix your outgoing interface name). e.g.
bash# ping6 -c 4 fe80::8014:74ff:fe20:38ab%eth0
PING fe80::8014:74ff:fe20:38ab%eth0(fe80::8014:74ff:fe2 0:38ab) 56 data bytes
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=1 ttl=64 time=0.687 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=2 ttl=64 time=0.174 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=3 ttl=64 time=0.267 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=4 ttl=64 time=0.187 ms

--- fe80::8014:74ff:fe20:38ab%eth0 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.174/0.328/0.687/0.211 ms

bash#

2. Add the following to /etc/sysconfig/network-scripts/ifcfg-eth0
IPV6INIT=yes
IPV6ADDR=/128
IPV6_DEFAULTGW=
IPV6_DEFAULTDEV=eth0

3. Add the following to /etc/sysconfig/network
NETWORKING_IPV6=yes

4. Restart networking
bash# systemctl restart network.service
bash#

5. Test it
bash# ping6 -c 4 ipv6.google.com
PING ipv6.google.com(par10s21-in-x0e.1e100.net) 56 data bytes
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=1 ttl=55 time=7.05 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=2 ttl=55 time=6.61 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=3 ttl=55 time=6.61 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=4 ttl=55 time=6.62 ms

--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 6.613/6.727/7.056/0.189 ms

bash#

That should do it !!

From where exactly did you get the IPv6 address to use? The problem is that most people are not assigned or routed an IPv6 address as far as I can see.

[SrvGuy]

Lol, if the configuration is really so complex, how about providing ready on-line converter + script builder. It would be trivial to do, if they want to server customers.

They sent ton of those IPv6 emails. Which contained invalid link which didn't work. And when I replied one of those mails and asked for working link, nobody has answered me for a about a week. - Typical.

[broker]

Not the best solution, but you can try TunnelBroker:

[mhmeadows63]

Progress !!

IPv6 addresses have started appearing in the OVH control panel for my servers in Strasbourg SBG1, though no sign yet for Gravelines GRA1.

Once you have been assigned your IPv6 address for a given server, apply the following steps to bring it to life:

1. establish your IPv6 default gateway link-local address

find the MAC address of your default g/w and calculate its link-local address (see EUI-64 Bit Address). e.g.
bash# ip neigh
51.254.112.1 dev eth0 lladdr 82:14:74:20:38:ab REACHABLE
bash#

Transform the MAC address into a link-local address (remembering to flip the 7th bit from the left).
82:14:74:20:38:ab => fe80::8014:74ff:fe20:38ab

Confirm your transformation (remember to suffix your outgoing interface name). e.g.
bash# ping6 -c 4 fe80::8014:74ff:fe20:38ab%eth0
PING fe80::8014:74ff:fe20:38ab%eth0(fe80::8014:74ff:fe2 0:38ab) 56 data bytes
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=1 ttl=64 time=0.687 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=2 ttl=64 time=0.174 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=3 ttl=64 time=0.267 ms
64 bytes from fe80::8014:74ff:fe20:38ab: icmp_seq=4 ttl=64 time=0.187 ms

--- fe80::8014:74ff:fe20:38ab%eth0 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3000ms
rtt min/avg/max/mdev = 0.174/0.328/0.687/0.211 ms

bash#

2. Add the following to /etc/sysconfig/network-scripts/ifcfg-eth0
IPV6INIT=yes
IPV6ADDR=/128
IPV6_DEFAULTGW=
IPV6_DEFAULTDEV=eth0

3. Add the following to /etc/sysconfig/network
NETWORKING_IPV6=yes

4. Restart networking
bash# systemctl restart network.service
bash#

5. Test it
bash# ping6 -c 4 ipv6.google.com
PING ipv6.google.com(par10s21-in-x0e.1e100.net) 56 data bytes
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=1 ttl=55 time=7.05 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=2 ttl=55 time=6.61 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=3 ttl=55 time=6.61 ms
64 bytes from par10s21-in-x0e.1e100.net: icmp_seq=4 ttl=55 time=6.62 ms

--- ipv6.google.com ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 6.613/6.727/7.056/0.189 ms

bash#

That should do it !!

[SrvGuy]

Just pinging on this topic. IPv6 would be nice, I had it with VPS Classic. All the other service providers which I'm using provide it. Truly including home, work, mobile network operators. Only one without IPv6 support is OVH.

Maybe it just magically pops up and becomes available at some time, as did the 16.04 for VPS 2016. If that happens, it would be nice to have short guide how to correctly configure it retroactively on VPS so it won't cause ton of wasted resources when people are tuning with it using obscure instructions from the net.

- Thank you

[Muhammad adnan]

Nowhere in the website says anything about IPv6 support, so I bet there's no ETA. The same as with IP FO.

I think OVH got a bit too fast with the new VPS Ranges. IPv6 & IP FO are too important to be set for later.

nice

[willieaames]

I have to admit the tunnelbroker registration and setup were absolutely painless, and it's been working flawlessly since. I'd argue they do more to promote IPv6 than most other organisation.

[chrisedwards]

I've also been using tunnelbroker, but looking forward to a more permanent solution without tunneling. This seems like something that's fairly standard on most other VPS'. Any update on when we can expect this from OVH on the VPS 2016 line?

[Nodens]

Thank you very much, this does look like a very interesting workaround for the time being. I will check it out on Monday and report back

[alvaroag]

Not the best solution, but you can try TunnelBroker:

https://tunnelbroker.net/

They will give you a IPv6 tunnel, so you can get a full /64 (Can get /48 if needed). It should work without problems on most distros, and requires little configuration.

BTW, if your server is located in BHS, your best option would be to choose the tunnel server in Toronto (216.66.38.58); if your server is located in RBX, the best options are Amsterdam (216.66.84.46), Frankfurt (216.66.80.30), and London (216.66.80.26 & 216.66.88.98).

[Nodens]

A few months have gone by and still no IPv6 support I really need my bind server to be reachable via IPv6

[Nodens]

Considering that the entire world is now enabling IPv6 and that OVH already has IPv6 infrastructure I thought it was a given. Why make new VPS packages without it when every old one supported it already. I mean how hard is it to pass addresses to the new VMs? It's not like we're expecting multiple IPv4 ips when there's a globla shortage on them, right?

EDIT: I just noticed this today on the control panel:
"IPv6 0/1"

This sounds like it's just a matter of IT resources in configuration..it looks like it's coming soon.

[alvaroag]

Nowhere in the website says anything about IPv6 support, so I bet there's no ETA. The same as with IP FO.

I think OVH got a bit too fast with the new VPS Ranges. IPv6 & IP FO are too important to be set for later.

[Nodens]

Hello,

I have switched to the 2016 VPS and to my surprise there is no IPv6 support. Can we get a timeframe on when it will be enabled for the 2016 VPS as I need IPv6 support.

Thanks