Opened 10 years ago
Closed 8 years ago
#13362 closed defect (obsolete)
Host-only interface for multiple users: VERR_INTNET_INCOMPATIBLE_FLAGS when DHCP server enabled
| Reported by: | wodny | Owned by: | |
|---|---|---|---|
| Component: | network | Version: | VirtualBox 3.2.10 |
| Keywords: | vboxnet dhcp restrictaccess | Cc: | |
| Guest type: | all | Host type: | Linux |
Description
A problem with host-only (vboxnet) interfaces when being used by multiple users has been already discussed. The solution is to setextradata VBoxInternal/Devices/e1000/<iface_index>/LUN#0/Config/RestrictAccess to 0 on all machines using the interface.
But it seems that, when the DHCP server is enabled for a host-only interface, the VBoxNetDHCP does not take those RestrictAccess settings into account. It starts first and creates a restricted interface. When machines later start, they are unable to switch that interface to the public security profile.
The error is:
Failed to construct 'e1000'/2! VERR_INTNET_INCOMPATIBLE_FLAGS (-3604) - The network already exists with a different security profile (restricted / public).
Is there any other workaround apart from disabling DHCP?
Attachments (1)
Change History (2)
by , 10 years ago
comment:1 by , 8 years ago
| Resolution: | → obsolete |
|---|---|
| Status: | new → closed |
Please reopen if still relevant with a recent VirtualBox release.
Note:
See TracTickets
for help on using tickets.
Partial log with VERR_INTNET_INCOMPATIBLE_FLAGS