Nat Network - VirtualBox 6.0 vs 6.1

[efixem]

Hi all,

I'm using VM's in Nat Network configuration. All is working fine with Oracle VirtualBox 6.0.

But now I want to migrate to Oracle VirtualBox 6.1 and existing VM's in the same Nat Network don't use this configuration.

. My Nat Network is configured as 192.168.15.0/24
. Vm receive good IP in OVB 6.0
. same VM don't receive a good IP in OVB 6.1

I tried, searched, recreated nat network .... but no solution for the moment. I continue to use 6.0 version.

Who can help me ?

Thanks in advance

Host: Windows 10
VM linux (Ubuntu 20.04 and 22.04)
Oracle VirtualBox: 6.0 - 6.1

[efixem]

Hi all,

Post is read, but no answer ...

Am I alone with this issue ?
Who can give me some tips to solve this issue ?
Is there a way to migrate from one version of Oracle Virtual Box to an other when using Nat Network ?

Please, I need tips and tricks or a least a way clue to solve it.

Tanks for your reading.
François

[mpack]

I found your initial post vague, and being too lazy to inquire further, I moved on.

Basically you say little more than "worked in 6.0.x" and "doesn't work in 6.1.x". E.g. if the VM doesn't receive a "good IP" in 6.1.x, then what does it receive? I'd also want evidence that you didn't configure the guest OS for static addressing.

A zipped VM log wouldn't hurt either.

Also there is no VirtualBox v6.0 and nor is there a v6.1. You should be precise about versions if you want someone else to try to reproduce the problem.

[efixem]

Hi @mpack,

First of all, thanks for your reaction.

About version of Oracle VirtualBox, I speak about last versions of 6.0 (VirtualBox-6.0.24-139119-Win) and 6.1 (VirtualBox-6.1.38-153438-Win).

When I say "work in 6.0 and not in 6.1", It means that a working VM in 6.0.24 receive a dynamic IP V4 address in the range of the Nat Network range (192.168.15/24) and when I start this VM in 6.1.38, this VM don't receive an IP address in this Nat Network range (see after for ifconfig output)

I also deleted de Nat Network definition made in 6.0.24 and recreate it in 6.1.38 before using it in 6.1.38: no change

The Guest Additional CD is also installed in 6.1.38.

You will also find the log files for both versions as asked.

Thanks for your feedback
François

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet6 fe80:4d6a:ce0c:d0f9 prefixlen 64 scopeid 0x20<link>
ether 08:00:27:95:6b:c3 txqueuelen 1000 (Ethernet)
RX packets 0 bytes 0 (0.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 3800 (3.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 18 bytes 2338 (2.3 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 18 bytes 2338 (2.3 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

[fth0]

As an educated guess, I'd suspect the name of the NAT network being part of the problem. "NatNetwork 15.0/24" contains a forward slash character, and VirtualBox uses file names derived from that name.

The easiest test would be to remove this NAT network and to create a new one without slashes (and spaces) in its name. If that works, you can try again with a space character.

If you want to investigate further, take a look at all configuration and log files in "C:\Users\A417735\.VirtualBox" that contain the name of your NAT network.

[efixem]

Hi fth0,

Thank you very much...removing the "/" in the Nat network name solves this problem

That "/" was not a problem for version 6.0.24 but is now for version 6.1.38 .

You make my day.
Issue can be closed

Regards
François