[u-u] VirtualBox and Vagrant

Hugh Gamble hugh at phaedrav.com
Fri Dec 5 16:50:39 EST 2014

VirtualBox defaults to NAT for the virtual NIC
If you're trying to get in there from outside it can be a double NAT.

When I'm running something like an HTTP server in the guest,
I set the virtual NIC to Bridged mode
(which causes it to use the same NAT as the host,
if your host is your dev workstation and it's already on NAT).

> -----Original Message-----
> From: u-u-bounces at unixunanimous.org [mailto:u-u-
> bounces at unixunanimous.org] On Behalf Of Greg A. Woods
> Sent: December-05-14 4:30 PM
> To: Unix Unanimous
> Subject: Re: [u-u] Virtualbox and Vagrant
> On 2014-12-05, at 1:06 PM, arocker at Vex.Net wrote:
> >
> > I'm trying to set up a test environment for a Web application, with
> > the server running in VB, accessible to a browser on my host machine.
> >
> > Using everything as out-of-the-box, I can ssh into the vagrant
> > machine, and ping the host. Attempting to ping the Vagrant address
> > from the host fails. (If ping doesn't work, I think it's safe to
> > assume that http
> > won't.) There does not appear to be any kind of firewall in the way.
> I wouldn't be so sure of that.
> I forget all the details, but if I'm not too drastically mistaken there is
a chance
> that there's a NAT in there somewhere.  I.e. ping may well fail, depending
on the
> NAT implementation, where a TCP connection works.
> In any case, the safest test is HTTP, or at least "telnet -n N.N.N.N 80"
> or similar.
> --
> 						Greg A. Woods
> -----
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2015.0.5577 / Virus Database: 4223/8634 - Release Date: 11/26/14
> Internal Virus Database is out of date.

More information about the u-u mailing list