- lucid32.box
- lucid64.box
- squeeze64.box
- talifun-ubuntu-11.04-server-amd64.box
- sl6-64-nochef.box
- ...
And the ones from http://files.vagrantup.com too:
- lucid32.box
- lucid64.box
All of them have been (re)downloaded less then 3 days ago.
Kind regards,
Tom
HTH,
Jan-Jaap
dhclient should be started by ifup when it brings the interface up, so
it should be set to auto and dhcp in /etc/network/interfaces. Something
along those lines:
auto eth0
iface eth0 inet dhcp
--
Babar.
The ssh issue might be connected to a dns issue or maybe the network
setup is triggering some thing else that ssh doesn't like.
I've set out one diagnosed case in issue #391[0]
Could others please indicate if they see the same things.
Note the SSH symptom shown is the same for multiple hosts on with one
IP and multiple redirects to one port so it shouldn't matter if you
have use hostbased networking or port redirection in your VM.
Hopefully this narrows down what the source of this is.
HTH?
[0]: https://github.com/mitchellh/vagrant/issues/391
--
πόλλ' οἶδ ἀλώπηξ, ἀλλ' ἐχῖνος ἓν μέγα
[The fox knows many things, but the hedgehog knows one big thing.]
Archilochus, Greek poet (c. 680 BC – c. 645 BC)
http://hedgehogshiatus.com
OK I've been able to reproduce the following:
1) `vagrant up` then continuously query `lsof -i :2222`
2) As soon as you see lsof show _one_ established connection (TCP
localhost:44716->localhost:2222 (ESTABLISHED)) , issue `ssh
vag...@127.0.0.1 -p 2222 -i vagrant` and you will be connected.
3) `vagrant reload` and now lsof will show two connections to 2222,
and you won't be able to ssh to your VM. Period. You have to
`vagrant halt`, then repeat step 1)
HTH
Hmm, this strategy also only succeeds intermittently.
Puzzled.
One more data point, on versions that do/don't work:
https://github.com/mitchellh/vagrant/issues/353#issuecomment-1326421
> On Sun, Jun 19, 2011 at 8:03 AM, Olivier Raginel <bab...@gmail.com> wrote:
>>
>> On Sat, Jun 18, 2011 at 06:26:46AM -0700, Rafael Chacon wrote:
>> > I don't know if is the best approach. But I add to command to dhclient
>> > to the /etc/rc.local and then every time that I restart the VM the
>> > network is properly configured and I'm able to do ssh.
>> >
>> > I noticed that dhclient it's not in /etc/init.d... maybe this is
>> > causing the problem in the box.... It's the first time that I'm using
>> > vagrant and virtualbox so I'm not quite sure if dhclient it's executed
>> > elsewhere...
>>
>> dhclient should be started by ifup when it brings the interface up, so
>> it should be set to auto and dhcp in /etc/network/interfaces. Something
>> along those lines:
>> auto eth0
>> iface eth0 inet dhcp
>>
>> --
>> Babar.
>
>
--
Pleasure, sorry if the tone sometimes seems on-edge. The more you see
the potential of something the more frustrating any hurdle is :)
And vagrant has the potential!
I'm beginning to think that what Oracle/Virtualbox (i.e. not the gem)
put out as patch version increment releases should probably be minor
version increment releases :(
Best wishes.