Ticket #1705 (closed enhancement: fixed)

Opened 13 years ago

Last modified 7 years ago

NAT/DHCP network setting support like VMWare does.

Reported by: AndCycle Owned by:
Component: network/NAT Version: VirtualBox 1.6.2
Keywords: Cc:
Guest type: other Host type: other

Description (last modified by frank) (diff)

VMWare scenario

  • VMWare Virtual Network Default
    • provide DHCP support at VMnet1/VMnet8 host interface
    • provide NAT support at VMnet8

we already got NAT support at VirtualBox, why bother?

well, because VirtualBox provide Direct NAT attach,
host can't connect to guest by NAT interface like VMWare does,
under VMWare, you can direct connect to guest that connect to NAT because they actually connect to the host interface that host knows where they are.

I do webapp develop with some firewall setting on VM,
and move it to production environment lately,

I want my guest can connect to internet to grab some web info,
and I have to access it's wan interface to test it.

if I wanna do this for VirtualBox,
it's simple under *nix environment, but pretty sucks under win32,

I used to work under my laptop with winXP,
the only DHCP/NAT in it is ICS(Internet Connection Sharing),
it sucks, it have to assign which interface as wan and which as lan,
it has bad DHCP ip range default that you have to change it from registry,
it won't auto switch with default routing when I roaming between wire/wireless internet.

that's why I want to have VMWare like NAT host interface support,
I only have to bridge it with VirtualBox host interface once, then everything will works like a charm.

Change History

comment:1 Changed 13 years ago by AndCycle

oops, VMWare installed DHCP/NAT service at Host to support this feature :X

comment:2 Changed 13 years ago by frank

  • Component changed from other to network

comment:3 Changed 13 years ago by RedCrayon

Also: enabling the host to see the NAT'ed virtual machine by IP address enables the host to share files (to a Solaris or Linux client) by NFS. I cannot use VirtualBox until such a feature is available; I use Fusion instead.

Note that, for Solaris clients, "folder sharing" isn't available, nor do I see that as a solution, if it's like the Fusion version: the files all appear to be owned by root, and there's no valid timestamp, etc. Nasty for developers.

The easiest solution is to allow the host to see the client IP, and set up specific NFS sharing, particularly from Solaris/Linux/OSX hosts to Solaris/Linux clients.

comment:4 Changed 12 years ago by frank

  • Component changed from network to network/NAT

comment:5 Changed 10 years ago by zsd


This is also an issue in places where the DHCP server will not give an unknown machine (ethernet addr) an IP, thus making it painful to use bridged networking.

comment:6 Changed 7 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed
  • Description modified (diff)

This kind of NAT support was added in VBox 4.3.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use