vagrant-based deployment fails due to weird case of 2 default interfaces

Here's what "ip route" gives on the host:

ip route
default via 10.0.2.2 dev eth0
default via 10.0.2.2 dev eth0 metric 100
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15

So yes, it's weird. But obvious workaround is to stop on first match...

Ok, I brought up bare http://files.vagrantup.com/precise64.box VM (box file downloaded couple of days ago). And it's the same:

vagrant@precise64:~$ ip route
default via 10.0.2.2 dev eth0
default via 10.0.2.2 dev eth0 metric 100
10.0.2.0/24 dev eth0 proto kernel scope link src 10.0.2.15

So, it's either vagrant or that image bug/feature.

Ah, just in case I also get:

[default] The guest additions on this VM do not match the install version of
VirtualBox! This may cause things such as forwarded ports, shared
folders, and more to not work properly. If any of those things fail on
this machine, please update the guest additions and repackage the
box.

Guest Additions Version: 4.2.0
VirtualBox Version: 4.1.12

I'm on precise (32bit) myself and use whatever VirtualBox version it ships.

See linked merge request for fix.