Page 1 of 1
Problems with Virtual Box NAT
Posted: 28. Jun 2009, 15:13
by Cossack
Hello everyone.
I'm having some problems with NAT on Vista Ultimate x64 , Virtual Box 2.2.4, Fedora 11 installed as a guest . I'm trying to make this thing work but without any success , ( VMware works as a charm and without any adjustments). I'm suspecting that some of VM ware drivers could conflict with Virtual box, but I can't uninstall VMware till I will be sure that it's causing problems. And what else I need to do to get NAT on my guest Fedora ( 8,11) and Ubuntu (9.04) ?
Re: Problems with Virtual Box NAT
Posted: 28. Jun 2009, 15:23
by Sasquatch
When creating this post, you should have seen a link to the
Forum Posting Guide, which you need to read if you want us to help you. What is your exact problem? What doesn't work and what do you expect to get?
Re: Problems with Virtual Box NAT
Posted: 28. Jun 2009, 18:50
by Cossack
Sasquatch wrote:When creating this post, you should have seen a link to the
Forum Posting Guide, which you need to read if you want us to help you. What is your exact problem? What doesn't work and what do you expect to get?
My exact problem : NAT doesn't work at all. During the installation on Vista Ultimate x64, VB created "Virtual Host-Only adapter" without any other options. Than I enabled NAT and selected adapter for guest connection .... Guest network interface captured correct tunes ( DHCP, domain name...etc ) but web is still not accessible for guest.
- I tried to use static protocol and use my host as a Gateway
- Marked vnat.exe as a "trusted" for the host firewall, disabled active armor in a BIOS
-Tried to modify rc.local in such way:
TUN=vbox0
IP=192.168.17.1
USERNAME=Cossack
tunctl -t $TUN -u $USERNAME
ifconfig $TUN up
ifconfig $TUN address $IP netmask 255.255.255.0
arp -Ds $IP $TUN pub
iptables -t nat -A POSTROUTING -j MASQUERADE
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/$TUN/proxy_arp
I'm expecting to get internet on my Guest OS
Re: Problems with Virtual Box NAT
Posted: 28. Jun 2009, 22:53
by Sasquatch
Ok, well, in that case, did you check the
VirtualBox FAQ for possible Firewall incompatibilities? There are some firewall software that just doesn't play nice with VB NAT.
As for the new adapter you got, that's got nothing to do with NAT. What you got is a virtual interface which you can configure through the VB global preferences. It's the Host-Only adapter that you can use to get a network between your VMs and your Host, totally separated from your physical network.