VirtualBox

Ticket #2554 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

host port forwarding stops working

Reported by: snblitz Owned by:
Priority: major Component: network/NAT
Version: VirtualBox 2.0.2 Keywords:
Cc: Guest type: Linux
Host type: Linux

Description

I have several Linux virtual machines running NAT'ed on a Linux host (all Ubuntu 8.04). Each has a port from the host mapped to port 80 in the guest, and a port from the host mapped to port 22.

 vbguest1: 2201 -> 22, 1081 -> 80
 vbguest2: 2202 -> 22, 1082 -> 80
 vbguest3: 2203 -> 22, 1083 -> 80
 vbguest4: 2204 -> 22, 1084 -> 80
 vbguest5: 2205 -> 22, 1085 -> 80

I also run openvpn in each slice connecting each to a private openvpn network. All guests are clients to a another physical machine that runs as an OpenVPN server elsewhere.

After 10 days of uptime one could no longer reach the web server or ssh server in vbguest1 via the host forwarded ports.

However, both the web server and the ssh server were reachable from the openvpn network. They also both worked correctly inside the slice.

Looking at the log files I could find nothing unusual anywhere.

I telnet'ed to host:1080 and the TCP/IP session would be negotiated, however no data would flow to or from the web server application in the guest.

The other slices were all working correctly. vbguest2 runs the same application suite as vbguest1. And the applications in vbguest2 were correctly accessible via the host forwarded ports.

Attachments

VBox.log.1 Download (52.6 KB) - added by snblitz 5 years ago.

Change History

comment:1 Changed 5 years ago by frank

The VBox.log file could be interesting in that case. And of course a testcase which does take less than 10 days ...

comment:2 Changed 5 years ago by snblitz

This situation just occurred again 2008-11-16 16:00. This is approximately 12 days since the previous occurrence. I would be willing to venture a guess that this condition will develop every 280 hours or thereabouts. I am attaching the vbox.log file.

Changed 5 years ago by snblitz

comment:3 Changed 5 years ago by snblitz

The situation occurred again after 283 hours (11 days 19 hours) of operation. The log did not look any different than the one I uploaded previously.

comment:4 Changed 5 years ago by frank

Any chance to test this with VirtualBox 2.1.0? There were massive changes in the NAT code ... Note that port forwarding is broken for Windows hosts in 2.1.0 but it should work for Linux hosts.

comment:5 Changed 5 years ago by snblitz

I will give it a try with 2.1.0

comment:6 Changed 5 years ago by frank

  • Component changed from network to network/NAT

comment:7 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

No response, closing. Before re-opening make sure to try the latest release VirtualBox 2.2.2.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use