Network issues on OS X 10.10 Yosemite

[lclemente]

I'm having trouble with guest network connectivity with Virtualbox 4.3.12r93733 running on OS X 10.10 Yosemite build 14A238x. There seem to be two issues with a Ubuntu Trusty VM i created using vagrant:

• Network connections (e.g. ssh sessions) to the VM keep hanging for 1-2min. When typing in ssh sometimes the shell is unresponsive for a couple of minutes.
• Network connections from the VM to the internet fail often (~50% ping drop), also this problem happens: ​http://stackoverflow.com/questions/24060099/docker-failed-to-pull-images-from-registry

I've tried: Restarting host / guest, recreating the VM, playing around with network settings (although I don't know much about that).

Let me know if you need any more details, I'm happy to help anyway I can.

[MrJoshua]

This is also causing problems with docker downloading images. Please upgrade the severity of this bug, it is show stopping for us.

[Louis King Jr]

try disabling Bluetooth on the Mac. There are issues with Bluetooth and WiFi both being on with 10.10. It has nothing to do with VirtualBox. I have been running Ubuntu 14.04 in VirtualBox since I installed 10.10.

[russianator]

Issue still occurs for me with bluetooth disabled

[Louis King Jr]

Replying to russianator:

Issue still occurs for me with bluetooth disabled

I suspect it's a problem with Vagrant. I don't use Vagrant so I can't check.

[KingGeekus]

Same issue, Mac 10.10 Beta + Vagrant +Ubuntu guest losing network repeatedly. Bluetooth on/off has no effect.

[KingGeekus]

This seems still unresolved under OS X 10.10 Beta 3

[maknz]

Having the exact same problems here with Vagrant / VirtualBox. Ubuntu 14.04. SSH is very unresponsive (about 1-2 minutes to login) and about the same for any input to be recognised. Also fails to connect to the Ubuntu package registry while provisioning (consistent with the network problems described here).

You can SSH into the Vagrant box without Vagrant with ssh vagrant@host -i /path/to/id_rsa, which does work instantly in getting a shell on the box (compared to severe lag with vagrant ssh). However, the network problems are still present.

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=63 time=9271 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=63 time=8270 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=63 time=7261 ms
64 bytes from 8.8.8.8: icmp_seq=4 ttl=63 time=6254 ms
64 bytes from 8.8.8.8: icmp_seq=5 ttl=63 time=5252 ms
64 bytes from 8.8.8.8: icmp_seq=6 ttl=63 time=4244 ms
64 bytes from 8.8.8.8: icmp_seq=7 ttl=63 time=3246 ms
64 bytes from 8.8.8.8: icmp_seq=8 ttl=63 time=2236 ms
64 bytes from 8.8.8.8: icmp_seq=9 ttl=63 time=1228 ms
64 bytes from 8.8.8.8: icmp_seq=10 ttl=63 time=227 ms
64 bytes from 8.8.8.8: icmp_seq=11 ttl=63 time=56.6 ms
64 bytes from 8.8.8.8: icmp_seq=12 ttl=63 time=56.0 ms
64 bytes from 8.8.8.8: icmp_seq=13 ttl=63 time=57.1 ms
64 bytes from 8.8.8.8: icmp_seq=14 ttl=63 time=56.9 ms
64 bytes from 8.8.8.8: icmp_seq=15 ttl=63 time=55.7 ms
64 bytes from 8.8.8.8: icmp_seq=16 ttl=63 time=56.5 ms
64 bytes from 8.8.8.8: icmp_seq=17 ttl=63 time=56.6 ms
64 bytes from 8.8.8.8: icmp_seq=18 ttl=63 time=55.8 ms

Trying again and the network has fallen over, but comes back...

$ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
From 10.0.2.15 icmp_seq=1 Destination Host Unreachable
From 10.0.2.15 icmp_seq=2 Destination Host Unreachable
From 10.0.2.15 icmp_seq=3 Destination Host Unreachable
From 10.0.2.15 icmp_seq=4 Destination Host Unreachable
From 10.0.2.15 icmp_seq=5 Destination Host Unreachable
...
From 10.0.2.15 icmp_seq=59 Destination Host Unreachable
From 10.0.2.15 icmp_seq=60 Destination Host Unreachable
64 bytes from 10.0.2.15: icmp_seq=61 ttl=63 time=357 ms
64 bytes from 10.0.2.15: icmp_seq=62 ttl=63 time=56.1 ms
64 bytes from 10.0.2.15: icmp_seq=63 ttl=63 time=56.7 ms
64 bytes from 10.0.2.15: icmp_seq=64 ttl=63 time=56.3 ms
64 bytes from 10.0.2.15: icmp_seq=65 ttl=63 time=56.2 ms
64 bytes from 10.0.2.15: icmp_seq=66 ttl=63 time=57.9 ms
64 bytes from 10.0.2.15: icmp_seq=67 ttl=63 time=56.7 ms
64 bytes from 10.0.2.15: icmp_seq=68 ttl=63 time=56.8 ms
64 bytes from 10.0.2.15: icmp_seq=69 ttl=63 time=56.6 ms
64 bytes from 10.0.2.15: icmp_seq=70 ttl=63 time=56.4 ms
From 10.0.2.15 icmp_seq=114 Destination Host Unreachable
From 10.0.2.15 icmp_seq=115 Destination Host Unreachable
From 10.0.2.15 icmp_seq=116 Destination Host Unreachable
From 10.0.2.15 icmp_seq=117 Destination Host Unreachable
From 10.0.2.15 icmp_seq=118 Destination Host Unreachable
From 10.0.2.15 icmp_seq=119 Destination Host Unreachable
From 10.0.2.15 icmp_seq=120 Destination Host Unreachable
...

I'm not sure what would cause Vagrant to hang on SSHing in, but the network problems must be related to VirtualBox?

Edit: This fix seems to have worked for me ​https://github.com/coreos/coreos-vagrant/issues/124#issuecomment-49481032. Vagrant ssh now works as before and networking is flawless :)

[Valery Ushakov]

Is this still a problem?

Suggested workaround linked in comment:7 turns off DNS proxy DNS host resolver, which obviously shouldn't affect ping.

Since initial OS X 10.10 release had known WiFi issues, I wonder if this is what you see here with 10.10 beta.