VirtualBox

Opened 17 years ago

Closed 16 years ago

#716 closed defect (invalid)

NAT problems => retry with VBox 1.5.4

Reported by: kimus Owned by:
Component: other Version: VirtualBox 1.5.0
Keywords: Cc:
Guest type: other Host type: other

Description

There are some 'problems' in NAT implementation.

I use this configuration to acess Apache HTTP Server from the Host to the Guest virtual machine: VBoxManage setextradata "vmname" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/Protocol" TCP VBoxManage setextradata "vmname" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/GuestPort" 80 VBoxManage setextradata "vmname" "VBoxInternal/Devices/pcnet/0/LUN#0/Config/Apache/HostPort" 8080

First if I put 80 instead of 8080 gives me an error. There is no application using port 80. Maybe this has to do with permissions because of the low port number.

Second, If the guest has a fixed IP then the NAT won't work because is expecting that the interface is configured to use DHCP !

Third, I can't use the VirtualHost's Apache configuration. example: accessing the url http://somehost:8080/ in the Host machine don't go to the correct page. If I do http://somehost/ in the Guest works fine!

I don't want to use bridging!!

Change History (4)

comment:1 by kimus, 17 years ago

If I save the Guest VM after I start the VM the NAT doesn't work again.

comment:2 by Frank Mehnert, 17 years ago

Your first problem: Yes, this is because of the low number. You cannot forward port 80 to the VM. I don't understand your second problem. Regarding your third problem: What is displayed in the browser if not the correct page?

Regarding your other comment: This bug was fixed in VirtualBox 1.5.4.

comment:3 by Frank Mehnert, 17 years ago

Summary: NAT problemsNAT problems => retry with VBox 1.5.4

comment:4 by Frank Mehnert, 16 years ago

Resolution: invalid
Status: newclosed

No response for ages, closing.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use