Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.


Oriphix

523 posts

Ultimate Geek
+1 received by user: 32


#207426 23-Dec-2016 22:23

Hi All,

So been trying to make this work for the past couple of days doing my head in.
Basically what I am trying to achieve is on my Windows 10 64bit machine I am running Hyper-V.
I want the VM which is a Linux Mint 18.1 to run on a different subnet.

I am unsure if the issue is on the Windows side or something I am missing in the Linux side.

Here goes:
My LAN network is: 192.168.20.x
Modem / Router IP is: 192.168.20.1
Model: Netcomm Wireless NF4V
Computer has one RJ45 port.
VM IP: 192.168.50.50

Computer -> Patch Panel -> Netcomm (port 3 at the back)

I have tagged the VM, V-Switch and NF4V as VLAN 2.








Not sure what I am missing here. The modem has random ports which die. I have to move the ports and if that dies I have to move it to another one. Not sure if its the modem thats doing something funny or actually a setting I missed somewhere.

Filter this topic showing only the reply marked as answer Create new topic
engedib
254 posts

Ultimate Geek
+1 received by user: 93


  #1694501 24-Dec-2016 01:25
Send private message

You will need to assign 192.168.50.1 to the VLAN2 interface on your router, configure NAT / routing and set this IP as a gateway on the linux VM

 

If the gateway is on a different subnet as per your screenshot, it won't work.





MCSE+M/S, MCITP




toyonut
1508 posts

Uber Geek
+1 received by user: 211


  #1694513 24-Dec-2016 07:29
Send private message

That config will never work. The basic IP configuration is wrong as per the first reply.

 

It may be easier to just run NAT on the virtual switch instead of trying to make it run through the router and mucking around with VLANs.

 

http://www.thomasmaurer.ch/2015/11/hyper-v-virtual-switch-using-nat-configuration/

 

This way, the virtual switch becomes like a router rather than a switch and anything behind it can be a different subnet.

 

Remove the VLANs, set up a virtual switch as per the link, join the VM to it.

 

If you are on the anniversary edition of Windows 10, use this link:

 

http://www.thomasmaurer.ch/2016/05/set-up-a-hyper-v-virtual-switch-using-a-nat-network/





Try Vultr using this link and get us both some credit:

 

http://www.vultr.com/?ref=7033587-3B


Oriphix

523 posts

Ultimate Geek
+1 received by user: 32


  #1694664 24-Dec-2016 19:44

@engedib and @toyonut - Thanks for the replies guys.

The Virtual Switch NAT worked like a charm. I didn't know you could do that in Hyper-V.
Learn something new everyday!
Thanks

Filter this topic showing only the reply marked as answer Create new topic








Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.