can´t set static IP address

[isobot]

Hardware: x86 based PC OS: Debian 11.1.0 Bullseye

Steps to reproduce:

VBoxManage hostonlyif create VBoxManage hostonlyif ipconfig vboxnet0 --ip 192.168.200.100 --netmask 255.255.255.254

VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available) VBoxManage: error: Context: "EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())" at line 242 of file VBoxManageHostonly.cpp

The same steps work fine when installing virtualbox-6.1_6.1.26-145957~Debian~buster_amd64.deb under Debian Bullseye

[Klaus Espenlaub]

Clearly documented in the changelog for 6.1.28... https://www.virtualbox.org/manual/ch06.html#network_hostonly

[isobot]

Replying to klaus:

Clearly documented in the changelog for 6.1.28... https://www.virtualbox.org/manual/ch06.html#network_hostonly

Sorry, but I can't find anything "clearly documented". The change log only says:

Network: More administrative control over host-only network ranges to prevent trouble due to misconfiguration, see user manual. Check updated documentation or your VMs may stop working!

But what actually was changed was this:

On Linux, Mac OS X and Solaris Oracle VM VirtualBox will only allow IP addresses in 192.168.56.0/21 range to be assigned to host-only adapters.

This is not more control, but less. It would be a good idea to hint at that new restriction in the change log.

[Klaus Espenlaub]

It gives the admin more control over what happens network wise on the system. Which of course limits what the user can do unless the admin gives him more than the default.

And what's unclear about the section in the manual? It does say how to define what's allowed, including an example which gives the user all the decision power back, restoring the previous behavior if the admin decides it's the right thing.

[isobot]

ok, you're correct. I was missing the part with /etc/vbox/networks.conf Reason is likely how I fast scan documentation. I stopped reading after ". For IPv6 only link-local ...", since I was not interested in IPv6 and didn't notice that IPv4 relevant information was following after.

I take the blame on me.