Three weeks ago, I mentioned having trouble in a NAT'd VirtualBox VM
with trying to do module installation.
There is a new VirtualBox release, 3.0.4, which corrects this problem.
It was broken since 3.0.0. From their ChangeLog:
| NAT: fixed passive ftp access to host server (bug #4427)
> Karl Kleinpaste wrote:
>
> > Trying to refresh from ftp.bible.org fails; it happens to hang Xiphos
> > forever. Trying a command line ftp program, I can get logged in, but
> > any commands are rejected with "500 I won't open a connection to
> > 10.0.2.15 (only to 71.206.198.112)", the latter of
Karl Kleinpaste wrote:
> Trying to refresh from ftp.bible.org fails; it happens to hang Xiphos
> forever. Trying a command line ftp program, I can get logged in, but
> any commands are rejected with "500 I won't open a connection to
> 10.0.2.15 (only to 71.206.198.112)", the latter of which is my
I can not help you, but have noticed that using VB in NAT has been
pretty odd and difficult. I certainly failed to make it work in the way
I wanted on a number of occasions.
Maybe you have more luck by creating a virtual network card (not sure
what the correct term is) whose IP is dependent on on
I'm on a residential-grade Comcast connection, behind a Linksys wireless
gateway, running a VirtualBox VM that fakes a NAT connection. So I'm 2
layers of NAT away from the reality of the public Comcast IP.
Trying to refresh from ftp.bible.org fails; it happens to hang Xiphos
forever. Trying a co
