4
So this might be a very basic and very stupid question but for the life of me I can not find an explanation on the web anywhere as to how this should work.
I have a very basic Hyper-V setup on my Windows 10 machine. I have two VM's one is a Mikrotik image and the other is lUbuntu. At this point I'm working on the most basic network configuration. I want the Mikrotik to behave as a router and firewall between the lUbuntu system and the outside.
I have two virtual network switches (VS) setup in Hyper-V. First the default switch (call it Outside) and second an internal switch (call it Inside) I created. The Mikrotik box has two VNIC's setup that are connected to the two switches. It acts as a DHCP-server on the VNIC which is connected to the Inside VNS.
If I look at my Host system (the Windows 10 I'm running the Hyper-V on) I see the expected two virtual switches as NIC's one vEthernet (Inside) and one vEthernet (Outside).
The issue I have is that the (Inside) NIC has a APIPA address. When I try to get it to renew the adress using ipconfig /renew the command times out. At the same time the Lubuntu system which has one VNIC which is connected to the (Inside) VS works just fine and gets an IP address from the appropriate pool right away.
So my first question is why does the Host system not behave the way I would expect with regards to a Hyper-V Virtual switch?
I assumed from what I read about Hyper-V virtual switches that the Host operating system should see it pretty much the same as a guest. Except it knows it's virtual I guess.
You need something on the internal network providing IP addresses. Either static IPs on each client on this network, or a DHCP server. – music2myear – 2018-12-24T23:15:17.950
@music2myear As the question states I have a Mikrotik router which is setup as a DHCP-server on the VNIC that is bound to the internal VS. – DRF – 2018-12-25T07:58:59.807
Either it is not providing the correct service, or the other VMs aren't finding that service. – music2myear – 2018-12-26T02:21:50.103
@music2myear The VM's are finding the service just fine. The lUbuntu VM gets an IP address no problem. The issue is with the Host OS not the VM's. – DRF – 2018-12-26T09:46:01.530
One more question: If the purpose of the Internal switch is to allow communication between the VMs and to provide communication Lubuntu to the Mikrotik, why didn't you choose a Private switch? The Private switch allows communication only between the VMs on your host and so sounds like the correct switch for the job. An Internal switch generally acts as a bridge on your host, allowing VMs access to host resources, which is not what it sounds like you are trying to do with that particular switch. – music2myear – 2018-12-26T16:13:06.500
@music2myear I understand the difference between a private switch and an internal switch. I would like to be able to communicate from the Host to the guests and vice versa. I don't quite understand what that has to do with why the Host doesn't seem to see the DHCP server on that NIC? – DRF – 2018-12-26T19:01:32.983
I have a similar setup, but am not running a DHCP server on my VM network. I just use static IPs because it's simpler and less likely to cause problems upstream if I have a misconfiguration. I have guesses as to why you're experiencing this, but research has not given any weight of proof to these guesses so far. – music2myear – 2018-12-26T19:21:11.937
Is by any chance your IP net work from your physical router (the one your windows 10 DHCP's form) conflicting with the one your mikrotik is handing out? (ie. are they in the same network?) – Edo Post – 2018-12-29T08:53:45.247
Could you perhaps also port your DHCP settings in the mirkrotik? – Edo Post – 2018-12-29T12:09:09.847
@EdoPost That's a good question but no. They are on different subnets. 89 and 88. – DRF – 2018-12-29T16:38:24.153
@DRF I see you accepted the answer, I’m guessing it’s solved now – Edo Post – 2018-12-29T20:27:00.457
@EdoPost Yes. Thank you for the responses but it turned out to be an issue with having left a default VLAN for the management OS setup. – DRF – 2018-12-29T22:44:25.397