Page MenuHomePhabricator

Enable IPv6 in vagrant vms
Open, LowPublic

Description

The IPv6 internets are expanding, and like everything else, our vagrant vms should have ipv6 support (of course, this is only any use if the host machine/network also has IPv6 support etc etc)

[22:44:10] <bd808> Something on the ipv4 route from my laptop to the cluster is slooooow. Things are fine over my ipv6 tunnel but all actions (apt, git clones) from inside my vms are crawling.
[00:01:57] <bd808> Reedy: It's my ISP I'm pretty sure. IPv4 traffic to eqiad is terribly slow. Ping time isn't too bad, but git clones and deb downloads slow to a crawl. Over my IPv6 tunnel things are fast, but the Vagrant managed VM doesn't get configured for IPv6 traffic.
[00:02:24] <Reedy> has someone not filed a bug about ipv6 support in our vagrant vms? heh
[00:02:38] <bd808> :)
[00:03:12] <bd808> I poked a bit to figure out if it was easy to enable. Turns out its not as far as I can tell.
[00:03:57] <bd808> random google searches say to use bridged networking if you want it
[00:04:36] <Reedy> guess that sorta makes sense
[00:05:06] <Reedy> Filed a bug for it anyway.. It may just be docs + config
[00:06:07] <bd808> Turning it on unconditionally would actually make things worse in the ipv4 only case since linux would do a AAAA lookup and timeout before moving on to the A lookup and connection.
[00:06:30] <bd808> I'll poke at the problem a bit more this evening

Event Timeline

Reedy raised the priority of this task from to Needs Triage.
Reedy updated the task description. (Show Details)
Reedy added a project: MediaWiki-Vagrant.
Reedy subscribed.
Reedy set Security to None.
bd808 subscribed.

This looks to be pretty tricky. VirtualBox is our default VM container. VirtualBox only supports IPv6 in "bridged" networking mode which places the VM on the same network as the host computer. There are known bugs with bridged networking and WiFi (1, 2). Other sources (3, 4) report that bridging has inherent limitations due to the design of the 802.11 protocol. In addition to the WiFi bridging problems, the VirtualBox DNS proxy that we use only supports IPv4 lookups (explicit AAAA queries return only A results) and the NFS file sharing feature requires a host-only network.

So we'd need to be ok with breaking on (some) WiFi connected hosts, disabling the DNS proxy optimization and either adding another network just for NFS or disabling it. Pretty lame all around. Maybe someday Oracle will decide that IPv6 is worth supporting in their product.

IPv6 support has apparently been available since Vagrant 1.8.0 (about a year after the comments in T85493#948577).