VirtualBox

Opened 9 years ago

Closed 9 years ago

Last modified 9 years ago

#13532 closed defect (worksforme)

NAT#0: Configuration error: network '10.0.%octet1%/8' describes not a valid IPv4 network

Reported by: Stephen Rondeau Owned by:
Component: network/NAT Version: VirtualBox 4.3.16
Keywords: Cc:
Guest type: other Host type: Linux

Description

This occurs in the log when starting a VM defined with NIC1 using NAT. There are many VMs using NAT at the time on different VMs; the actual message the user saw when using "VBoxManage startvm" is:

VBoxManage: error: NAT#0: Configuration error: network '10.0.30400107640ctet18' describes not a valid IPv4 network (VERR_INVALID_PARAMETER). VBoxManage: error: Failed to attach the network LUN (VERR_INVALID_PARAMETER) VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Consol e, interface IConsole

I had this happen for two different VM users and two different guest OSes.

Attachments (1)

VBox.log (33.4 KB ) - added by Stephen Rondeau 9 years ago.
VirtualBox log file

Download all attachments as: .zip

Change History (7)

by Stephen Rondeau, 9 years ago

Attachment: VBox.log added

VirtualBox log file

comment:1 by Stephen Rondeau, 9 years ago

Although I could not figure out how to fix the problem, there is a workaround -- define a different NAT network; e.g.:

VBoxManage modifyvm ubuntu --natnet1 "10.1.2/24"

comment:2 by Frank Mehnert, 9 years ago

What is the output of 'VBoxManage getextradata ubuntu enumerate'? To me it looks like you tried to override the network using an invalidate network specification.

Version 0, edited 9 years ago by Frank Mehnert (next)

in reply to:  2 comment:3 by Stephen Rondeau, 9 years ago

Replying to frank:

What is the output of 'VBoxManage getextradata ubuntu enumerate'? To me it looks like you tried to override the network using an invalid network specification.

Although that command returned nothing, pointing the finger back in my direction made me think more about the error. I realized it was a user error, so this ticket can be closed.

comment:4 by Frank Mehnert, 9 years ago

Resolution: worksforme
Status: newclosed

Thanks you for this information!

in reply to:  4 comment:5 by Stephen Rondeau, 9 years ago

Replying to frank:

Thanks you for this information!

It could still be an error, since VBoxManage accepted an invalid configuration:

VBoxManage modifyvm ubuntu_250 --nic1 nat --natnet1 10.0.%octet1%/8

My script was supposed to replaced %octet1% with a valid octet before issuing the command, but didn't. So the IPv4 subnet specified was invalid. If it had not have been accepted in the first place, the VM would have kept its original settings and the user would seen an error message but would have been able to start the VM.

I changed my script to provide a valid octet, but I think syntax-checking in the --natnetx value would be beneficial.

comment:6 by Frank Mehnert, 9 years ago

Well, there could be a sanity check but OTOH VBoxManage is not the universal tool, it's more a helper for functions which are not implemented in the GUI and which require more low-level knowledge. So I don't expect that anybody has time to spend time to implement a proper check here.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use