The VM Mikrotik machine configured with two NIC's with oneĬonnected to the "internal" Hyper-V switch (inside) that has the DHCP service running on it, and the other is connected to an "external" Hyper-V switch (outside), etc.
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. 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?
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. When I try to get it to renew the adress using ipconfig /renew the command times out. The issue I have is that the (Inside) NIC has a APIPA address. 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). It acts as a DHCP-server on the VNIC which is connected to the Inside VNS. The Mikrotik box has two VNIC's setup that are connected to the two switches. First the default switch (call it Outside) and second an internal switch (call it Inside) I created. I have two virtual network switches (VS) setup in Hyper-V. I want the Mikrotik to behave as a router and firewall between the lUbuntu system and the outside. At this point I'm working on the most basic network configuration. I have two VM's one is a Mikrotik image and the other is lUbuntu. I have a very basic Hyper-V setup on my Windows 10 machine.
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.
0 kommentar(er)
