Failed to create internal network - bridge with VLAN
Posted: 4. May 2015, 12:14
Hi,
I am trying to set up an "Internet VM" on a desktop LAN.
The LAN is a classical LAN without VLANS. There are Windows systems that we do not want to connect to the Internet. All IP are statics. This LAN is running IPv4 only.
I have added a Linux box somewhere on the LAN. On this Linux, there is a NIC with a VLAN n°42, and this VLAN is bridged to the Internet modem, that provides a DHCP service. This part works.
Somewhere else on the LAN, on a Windows Seven computer with a Realtek NIC, I have done the following setup :
- Installed the Realtek Diagnostic tool,
- Used this Realtek tool to add a virtual NIC, on VLAN 42,
- Fixed the physical Realtek NIC that lost its IP config after the VLAN setup (I had to re-check the IPv4 checkbox in connection properties),
- Installed VirtualBox,
- Created a Linux Debian VM on VirtualBox,
- Set up the Card1 of Debian VM to bridge link with the virtual Realtek,
- Tried to start the VM.
I got the following error message :
"Failed to open/create the internal network 'HostInterfaceNetworking-Realtek Virtual Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND)
Failed to attach the network LUN (VERR-INTNET_FLT_IF_NOT_FOUND)."
I would like to know what is the correct setup to do what I want, that is :
- the "legacy" LAN with no VLAN and static IP Windows talking to each others,
- the VLAN42 providing Internet using DHCP, through VLAN option of NIC, to the Linux VM, inside the Windows 7 host.
Windows 7 show three network interfaces : the Physical Realtek, the VirtualBox Host Only, and the Virtual Realtek.
There are many options for each network interface (on/off IPv4, on/off Realtek VLAN, on/off VirtualBox Host interface..), and I am a bit lost there.
I am trying to set up an "Internet VM" on a desktop LAN.
The LAN is a classical LAN without VLANS. There are Windows systems that we do not want to connect to the Internet. All IP are statics. This LAN is running IPv4 only.
I have added a Linux box somewhere on the LAN. On this Linux, there is a NIC with a VLAN n°42, and this VLAN is bridged to the Internet modem, that provides a DHCP service. This part works.
Somewhere else on the LAN, on a Windows Seven computer with a Realtek NIC, I have done the following setup :
- Installed the Realtek Diagnostic tool,
- Used this Realtek tool to add a virtual NIC, on VLAN 42,
- Fixed the physical Realtek NIC that lost its IP config after the VLAN setup (I had to re-check the IPv4 checkbox in connection properties),
- Installed VirtualBox,
- Created a Linux Debian VM on VirtualBox,
- Set up the Card1 of Debian VM to bridge link with the virtual Realtek,
- Tried to start the VM.
I got the following error message :
"Failed to open/create the internal network 'HostInterfaceNetworking-Realtek Virtual Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND)
Failed to attach the network LUN (VERR-INTNET_FLT_IF_NOT_FOUND)."
I would like to know what is the correct setup to do what I want, that is :
- the "legacy" LAN with no VLAN and static IP Windows talking to each others,
- the VLAN42 providing Internet using DHCP, through VLAN option of NIC, to the Linux VM, inside the Windows 7 host.
Windows 7 show three network interfaces : the Physical Realtek, the VirtualBox Host Only, and the Virtual Realtek.
There are many options for each network interface (on/off IPv4, on/off Realtek VLAN, on/off VirtualBox Host interface..), and I am a bit lost there.