Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

IPv6 support #32

Open
rhertzog opened this issue Oct 31, 2016 · 23 comments
Open

IPv6 support #32

rhertzog opened this issue Oct 31, 2016 · 23 comments

Comments

@rhertzog
Copy link

Before using Overthebox, I had a fully working IPv6. Now with the overthebox, that's no longer the case (I noticed the integrated DNS servers even drops the AAAA answers) which means that even though I might still have working IPv6 via one of the underlying modems, it's never used in practice.

Now I bought the overbox anyway because I saw some promises in the FAQ here:
https://www.ovh.com/fr/g2242.faq_overthebox#faq_overthebox_est-ce_que_lipv6_est_supportee

It says that you are working on IPv6. I thus open this ticket to publicly track the status of IPv6 support. What's the current status and how far are you from having working IPv6 support?

I can gladly help beta-test if needed.

@angt
Copy link
Contributor

angt commented Oct 31, 2016

Hi,
I confirm that the current version does not support IPv6 but it's scheduled for next release (0.5).
You may want to take a look at the corresponding PR to see how it's implemented: ovh/overthebox-feeds#118
Regards.

@rhertzog
Copy link
Author

What's the status of IPv6 support?

@angt
Copy link
Contributor

angt commented Mar 30, 2018

Hi @rhertzog,
We do not work directly on IPv6 because (very) few customers ask for it but the current R&D (infra and tunnels) should greatly simplify its use.

@rhertzog
Copy link
Author

FTR I am a customer and I know that IPv6 is not important for most end users but still we should all work towards IPv6 support because it's getting more and more urgent. And the global IPv6 traffic is growing. And it's a pity that I can't use it when both of my underlying network connection do provide working IPv6. That's the only thing that I lost when I started to use my overthebox and the first thing that I requested.

Let me know when you have something in beta-test or any documentation explaining how to set it up.

@Adorfer
Copy link

Adorfer commented May 4, 2018

no ipv6 is a blocking point (for not signing up), since both existing providers offer DualStack with fixed-v4/fixed-v6prefix.

@B4rb3rouss
Copy link

ipv6 would be very useful for me. I almost did not bought OTB because of missing ipv6.

@angt
Copy link
Contributor

angt commented Jun 12, 2018

Hi,
I confirm that the new infra will allow us to provide a full ipv4/ipv6 dualstack.
There is still a lot of work to be done tho.

@B4rb3rouss
Copy link

B4rb3rouss commented Jun 12, 2018 via email

@angt
Copy link
Contributor

angt commented Jun 12, 2018

It is a very big update and we'll upgrade clients step by step.
We hope to finish this before 2019.

@Adorfer
Copy link

Adorfer commented Nov 29, 2018

1 month to go until 2019... not losing hope. (a not-yet customer of OTB)

wesraph pushed a commit to wesraph/overthebox that referenced this issue Dec 12, 2018
… to release/53

* commit 'd59f5183d3c6ea8e61a88ba2ef1755574385d9d7':
  check if overthebox deamon is running and fix postinstall script
wesraph pushed a commit to wesraph/overthebox that referenced this issue Dec 12, 2018
overthebox: check if there is no headers
@angt
Copy link
Contributor

angt commented Jan 30, 2019

Hi, just to inform that i've pinged the first IPv6 today on our new infra !
We'll take the time to make it available on the device, but things are moving forward :)

PING 2001:41d0:ffc0::1(2001:41d0:ffc0::1) 56 data bytes
64 bytes from 2001:41d0:ffc0::1: icmp_seq=1 ttl=57 time=22.10 ms
64 bytes from 2001:41d0:ffc0::1: icmp_seq=2 ttl=57 time=23.9 ms
64 bytes from 2001:41d0:ffc0::1: icmp_seq=3 ttl=57 time=22.3 ms
^C
--- 2001:41d0:ffc0::1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 5ms
rtt min/avg/max/mdev = 22.349/23.072/23.871/0.635 ms

@Adorfer
Copy link

Adorfer commented May 9, 2019

Any news on the topic? missing ipv6 is really blocking us from signing up.

@Maxence
Copy link

Maxence commented Jul 1, 2019

Hello, any news about IPv6 support ?

@romanouille
Copy link

Hi, there's news about IPv6? I need IPv6 and I think it would be strange to have to configure a tunnel to have IPv6... in 2019. I intend to have an overthebox but the lack of IPv6 is boring, especially when we have the intend to host services on the overthebox which are all IPv6-ready. Being forced to disable IPv6/configure a tunnel... it's not too much in my ideas.

@angt
Copy link
Contributor

angt commented Sep 8, 2019

Hi all,
IPv6 is on the road as you know but this feature requires a lot of work (mainly on security) and is not our priority. That said, glorytun support IPv6 (with IPv4 on the same socket) so you can already test dual-stack aggregation with a (virtual) server.

@angt
Copy link
Contributor

angt commented Oct 5, 2019

overthebox version 0.7 will handle ipv6 (real full dual-stack, no 6rd,...):

root@OverTheBox:/# ping6 google.com
PING google.com (2a00:1450:4007:80f::200e): 56 data bytes
64 bytes from 2a00:1450:4007:80f::200e: seq=0 ttl=55 time=17.296 ms                                                        
64 bytes from 2a00:1450:4007:80f::200e: seq=1 ttl=55 time=17.744 ms
64 bytes from 2a00:1450:4007:80f::200e: seq=2 ttl=55 time=17.352 ms                                                        
64 bytes from 2a00:1450:4007:80f::200e: seq=3 ttl=55 time=17.678 ms
64 bytes from 2a00:1450:4007:80f::200e: seq=4 ttl=55 time=17.576 ms

The tunnel forward ipv4 and ipv6 and all devices will have full dual-stack.
But we still need ipv4 connectivity to get the service. Also we plan to give a /56.

@benoitc
Copy link

benoitc commented Jan 27, 2020

what is the status of it?

@Adorfer
Copy link

Adorfer commented Feb 2, 2020

the versioning here in the git ("master" is certainly ahead for 0.5), supposedly "master" is "0.6",
but the images for download in "/dev" are named like:
"overthebox-v4.9-v0.6.22-224"
So probably the "v4.9" has to be fully ingnored and the dev snapshots are "0.6.22".
In other words: nothing to test in terms of "v" 0.7

@angt
Copy link
Contributor

angt commented Feb 2, 2020

Hello,
The current versioning is not easy to follow I admit. v0.7 is the next version of overthebox-feeds (master branch). v4.x is about the base image (repo overthebox). For IPv6, things keep going :)

@poVoq
Copy link

poVoq commented Mar 25, 2020

Any approximate ETA for the update to the service?

@angt
Copy link
Contributor

angt commented Mar 25, 2020

Hello,
IPv6 is ready technically, there is no ETA, sorry.
Regards.

@Adorfer
Copy link

Adorfer commented Apr 1, 2020

if it's "technically ready": it should make sense for one of us customers to (re-)open a thread in the forum, in order to push for it on the commercial side.

@ObiYoann
Copy link

Hi every one, I sent a message to the OVH support team on twitter and nothing seems to evolve regarding the support of ipv6 on overthebox.
https://twitter.com/ovh_support_fr/status/1319638426766004224
We still have no other solution than to wait unfortunately...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

9 participants