So, you're saying that the host only passes it's own MAC, etc. to the network?!
I am saying that in my limited tinkering that a machine running virtualized devices is viewed by its' network as one
thing, the term I think is node. I find consideration of VMs as physical devices helpful here when considering their relationship to actual physical devices.
The VM doesn't have means to do anything without the host intercepting its Output, routing it to physical and then when data returns once again provide that to the VM as Input. The host does the talking for its children, and phrased my MAC address statement incorrectly. It's been a while since I dug deep into understanding transfer layers of data in TCP/IP but you can test the very basics quite simply on your network.
Does the VM have Internet access?
Does the DHCP of your physical network recognize the VM seperate from its host OS?
What address, subnet and gateway is the VM showing?
What address range and subnet is your lmce network using?
I am sure there is some way to work a pass through with added NICs. Physical devices on a host machine are resources that can be shared between specified VMs or allocated exclusively to one. This setup is beyond my experience however so I can not provide the setting details.
The force it and see if it works method I would attempt would be pick a number and try it. Under add new device in lmce I would test by calling it a file server. Set new device number to _._.80.253. Go to your VM and set it to _._.80.253 on subnet 255.255.255.0, gateway1 <host os ip> gateway 2 = _._.80.1. Reload router and see if it's listed as a dhcp lease.
Talking to and taking ownership of are very different keep in mind and these are early connection tests only. To have this setup working properly you ultimately need to adjust settings so that when the VM boots and yells "can I get an IP please?", the core is the one who hears that and says "sure! But let me look at you first and see if you are any good to me."
