7.0.10 port forwarding displays wrong values

[Dmitry Berezovik]

Port forwarding displays wrong values. Step to reproduce: 1) create port fowarding (NAT) using GUI 2) start VM -> connection refused 3) stop VM -> remove port forwarding 4) create port forwarding using CLI VBoxManage command 5) start VM -> works fine 6) open GUI settings for Port forwarding 7) Displayed values are wrong: 33 instead of 22, 9554 instead 8443. The values in .vbox config file are correct

[Dmitry Berezovik]

sreen

[fth0]

Hmmm, that looks and sounds strange. Can you provide a VBox.log file from a VM run?

[Dmitry Berezovik]

VBox logs

[Dmitry Berezovik]

Added logs to attachments

[fth0]

Thanks for the log files. In VBox.log.3, the port numbers 1111 and 7332 occur (negative offset: -1111). Did you perhaps use those port numbers deliberately in the past?

[Dmitry Berezovik]

Nope. Looks like those are the value that got into config when I entered 2222 and 8443 using GUI

[Dmitry Berezovik]

I guess for some weird reasons GUI and config values differs by 1111. The ones in config file work.

[fth0]

Could there be some i18n (internationalization) issue involved?

[Dmitry Berezovik]

I don't know, maybe... Is there any way to check?

[fth0]

For a start, you could tell us about your Windows language setting and your keyboard.

At the moment, I'm fishing for ideas. You already had the issue with VirtualBox 7.0.8, and if more users had the same problem, we'd probably have heard about it. So the question is: What makes your setup special?

[Dmitry Berezovik]

Device name: dberezovik Full device name: dberezovik.scnsoft.com Processor: Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz 2.70 GHz Installed RAM: 16.0 GB (15.9 GB usable) System type: 64-bit operating system, x64-based processor Pen and touch: No pen or touch input is available for this display

Edition: Windows 10 Enterprise Version: 21H2 Installed on: 5/‎26/‎2022 OS build: 19044.3448 Experience: Windows Feature Experience Pack 1000.19044.1000.0

Country: US Current format: English (US) Display language: English (US) Preferred language: English (US), Russian Keyboard layouts: English (US), Russian Time zone: UTC+03:00 Istambul

[fth0]

Looking at scnsoft.com, I noticed that you also work with Qt. Since the VirtualBox Manager is based on QT5 and brings its own QT libraries with it, do you perhaps have QT settings in your host OS that might interfere with VirtualBox?

If this doesn't give any further insights, you might try the following experiment: Using VBoxManage, configure the port number 2229 (with a "9"), and using the VirtualBox Manager, configure the port number 2220 (with a "0"). What happens to those port numbers?

[Dmitry Berezovik]

1) Setting 2229 using VBoxManage makes UI to display "333:" 2) VirtualBox Manager does not allow to set 2220 and changes it to 2221 when clicking outside the field. Config file displays 1110 in this case

My host is not related to any of our QT projects

[fth0]

Thanks for trying! :) How did you try to set 2220, by keyboard input or via the QSpinBox controls? What happens if you use the QSpinBox controls to increase or decrease the number more than ten times? Try to experiment a bit.

Regarding Qt in general, did you setup your host yourself, or does it have a base setup made by an IT department or similar?

[mtekjonas]

We have also experienced this on an Azure Virtual Desktop running Windows 11 as host OS, with VirtualBox version 7.0.12 r159484 (Qt5.15.2).

We're setting everything in the UI. When checking with netstat on the (virtual) host OS we see that any digit in NAT settings except for zero (0) are subtracted by 1. This means that if we use the common scenario to set up NAT for SSH to forward port 2222 to port 22, Virtualbox is listening on port 1111.

Port forwarding port 5007 makes Virtualbox listen on port 4006, etc.

Update: It works when configuring through CLI VBoxManage so it seems to be GUI related. Other installs using the same environment, versions, etc work without issue.

[Klaus Espenlaub]

We need a way to reproduce... all our attempts so far have failed. We see the values in the GUI making it directly to the listen port numbers.