VirtualBox

Ticket #8796 (new defect)

Opened 3 years ago

Last modified 4 months ago

Host-only adapter interface lost it's manual configured ipv4 address

Reported by: kidault Owned by:
Priority: major Component: network/hostif
Version: VirtualBox 4.0.6 Keywords: address
Cc: Guest type: Windows
Host type: Windows

Description

I have a host-only interface created by 2.x long time ago. After installation of 4.0.6, I find I have to re-configure the ip address of host-only interface after every reboot. The ip address is manually configured by vbox manager gui, and then I add gateway and dns server in the ipv4 properties。 After reboot,the configuration in the ipv4 properties seems not changed, but in the vbox manager gui, the ip address will be something like "169.254.4.67", and the ipconfig.exe command will show the same address.

Change History

comment:1 Changed 3 years ago by kidault

not fixed in 4.0.8

comment:2 follow-up: ↓ 3 Changed 3 years ago by diagiman

I have the same on host Win7x64.
And as I figured out problem is in net mask
VBox wants to use 255.255.0.0 mask and when I give it my IP with 255.255.255.0 mask, it refuses it and uses self-generated IP 169.254.*.* with /16 net mask.
But when I type my preferred IP with 255.255.0.0 it goes OK

It is quite reproducible (at every VBox update)

comment:3 in reply to: ↑ 2 Changed 3 years ago by kidault

Replying to diagiman:

I have the same on host Win7x64.
And as I figured out problem is in net mask
VBox wants to use 255.255.0.0 mask and when I give it my IP with 255.255.255.0 mask, it refuses it and uses self-generated IP 169.254.*.* with /16 net mask.
But when I type my preferred IP with 255.255.0.0 it goes OK

It is quite reproducible (at every VBox update)

Thank you for the solution. At least, I won't have to set the ip address after every host reboot. But I have never encounted with this problem until 4.0.6. I used to set ip of host-only interface as 192.168.56.1/24, and this setting had worked well all the time until 4.0.6

comment:4 Changed 2 years ago by kidault

The problem seems to have been solved in 4.1.4, thank you.

comment:5 Changed 2 years ago by Cyber1000

I have the setting 192.168.100.1/24. Everytime I update virtualbox (Win7x64) it goes back to 192.168.56.1/24. Also at update from 4.1.4 to 4.1.6. I have this problem at least since Version 4.0, but I don't have the problem after reboot, when I change the address back after install it stays the same until the next update.

comment:6 Changed 2 years ago by Zarko

I recently upgraded to 4.1.10 r76795 (from the previous latest version ... not sure which) on Windows XP and I can verify that my setting of 192.168.2.1/24 was reverted as stated above.

comment:7 Changed 2 years ago by mk8

On my Windows7-64bit installation I have the same problem.

I try to change the address from 192.168.56.1 to 192.168.56.2 and the changed seems to be accepted. Coming back in the ipv4 setup now I have two address, 192.168.56.1 and 192.168.56.2. If I remove the 192.168.56.1 the interface address came back to 169.254.219.

Now if I reboot the machine, the address remain 192.168.56.2.

For now this is the only workaround that I found.

comment:8 Changed 2 years ago by mk8

Update to 4.1.12r77245 and the problem continues to be present.

Fortunally the workaround is the same, change the local address from 192.168.56.1 to 192.168.56.2.

comment:9 Changed 2 years ago by jinzapper

I can confirm that this issue exists for 4.1.14r77440. Work around is the same, for me, editing the subnet mask or address did the trick. Interestingly, this problem only came up to me when I upgraded to 4.1.14 from 4.1.12. I did not have this previously.

comment:10 Changed 8 months ago by rousseauhk

I'm still seeing this on 4.2.16 with a number of hosts (but not all).

comment:11 Changed 7 months ago by apchoo

I have 2 host-only ethernet adapters and I've have no problems with their manual configs until I upgraded to 4.2.18 (from 4.2.16). Now that I'm on 4.2.18, my manual IP and netmask settings for "Virtual Host-Only Ethernet Adapter" always reverted back to 169.254.x.x and 255.255.0.0 after I pressed OK on the Preferences and Windows UAC windows. The settings for the 2nd "Virtual Host-Only Ethernet Adapter 2" do stick.

My workaround is to create a 3rd "Virtual Host-Only Ethernet Adapter 3" whose settings fortunately did stick as well. I have to re-configure all my VMs to use adapters 2 & 3 instead.

My VirtualBox host env is a Windows 7 Enterprise 64bit running on a Dell Precision M4700 laptop with 32GB memory.

comment:12 Changed 4 months ago by JohnnyCanuck

I can confirm the report from 'apchoo' with my Windows 7 Home Premium workstation and VirtualBox 4.2.18. As a result, I can't use 'Host Only' unless I perform the workaround (s)he describes.

On the other hand, maybe I'll try using the 169.254.X.X range and see what happens.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use