Isolate Virtual Machine from rest of LAN -- w/ access to Router/WAN

rowebil

Honorable
Feb 5, 2013
18
0
10,510
I have a cable modem going into a router with Tomato. The router network is my home LAN. From the router, I have an Ethernet cable to a gigabit switch. From that switch, I have a single Ethernet Gigabit cable going down into the basement to my rack.
It goes into a Netgear 24 port Gigabit switch, which connects my (3) physical ProLiant servers, each having 2 NIC's.

One NIC on the one server, goes to vSphere which has my Active Directory and DHCP installed. It is the main center for my home network. It hosts anti-virus virtual machines (something like VirusTotal with 35+ scanning engines), automation systems, and FreePBX.

The other NIC goes to nothing, and is unused.

I want to create a virtual machine, using the second NIC (unused) as the network interface. Keep in mind, that NIC goes to a switch that goes to a single wire leading to the middle floor switch into the router.

I do not want this virtual machine to have access to my LAN. My friend needs access to a server, so I thought I'd allow him to do our project with my server. He is not tech-savy, but I am curious on his intentions if he finds access to my computer, shared drives, etc.

I can enable VLAN for the vSphere network (second NIC) and then enable it on Tomato.
However, the Tomato router has only ONE Ethernet wire connecting everything. I cannot get it to do VLAN tagging, which I suspect would allow me to use one LAN port (on the router) to separate VLAN 0 ( my home LAN) and VLAN 12 (vSphere VLAN to isolated VM). But it is disabled, and I cannot get the VLAN tagging enabled.



So -- how do I approach this?
Would it be simple enough to change the IP scheme? I know basic network - IP addressing - subnetting - but am not entirely sure if changing the subnet will restrict access to my home LAN. If so, then he won't be able to get to the router (connected to modem).

Is a VLAN the correct way? Can I run my home LAN and a VLAN on the same wire to the Tomato router?

Another way, can't I just install pfSense with a WAN port coming from the NIC#2 and the LAN would be virtual network with vSphere. The VM will connect to pfSense box. Then, can I set firewall rules to ONLY accept communication to and from my router-to-modem? Then he won't be able to ping or contact my local machines due to firewall rules. Correct?
 
Solution
Would be nice if you had managed switches in the path that you could use vlan tags on then you could use a simple vlan design.

As I suspect you are suggesting you can just run both "vlans" directly overlapping each other. Pretty much you are depending on the machine being stupid and no hacking users. You could say take a switch and plug 2 machines say using 10.10.10.1/24 and 10.10.10.2/24 and a second pair of machines using 10.100.100.1/24 and 10.100.100.2/24. This will work because the machine do not issue arp command for devices outside their subnet. They would send the traffic to the default gateway on their subnet and if there was no connection between the gateway. As long as the users do not know what the other subnet is or...
Would be nice if you had managed switches in the path that you could use vlan tags on then you could use a simple vlan design.

As I suspect you are suggesting you can just run both "vlans" directly overlapping each other. Pretty much you are depending on the machine being stupid and no hacking users. You could say take a switch and plug 2 machines say using 10.10.10.1/24 and 10.10.10.2/24 and a second pair of machines using 10.100.100.1/24 and 10.100.100.2/24. This will work because the machine do not issue arp command for devices outside their subnet. They would send the traffic to the default gateway on their subnet and if there was no connection between the gateway. As long as the users do not know what the other subnet is or you rig it so they can not change the ip address the traffic will stay isolated...other than some small amount of broadcast traffic.

So what you can do is assign this virtual machine a completely different subnet. On your tomato router you would assign a secondary IP in that subnet. So now the same interface has 2 ip in the tomato....in effect a virtual interface that is extremely non standard. What you would then do is put in rules with the IPtables command to prevent any traffic from going between these networks but allow it to go to the internet.

It is really a hack but your only real option without switches that support vlans.
 
Solution