Simplest Way to Create a Lab network , in production env?

June 7, 2019 at 04:14:11
Specs: Windows 10, Ryzen 1600, 32GB Dominator RAM
I know how this can work and have done it before ( method 1 below ) but, I am not sure this is the simplest method and have some other ideas :

Method 1: ( Tried and tested ) Connect an additional Router , using its WAN port on the Production network , Create a new subnet

Method 2 (Idea ) . Add a Lynksys Tomato Router , create separate VLAN for the LAB . I have been toying with this for a while but , I cannot get the lab VLAN to connect to the internet

Method one , requires two connections for my desk space , getting a new connection will be a pain and requires additional equiptment ( A switch and a router ) on desk .
Method 2 if possible could just require one connection and one device on my desk

message edited by 90Ninety

See More: Simplest Way to Create a Lab network , in production env?

Reply ↓  Report •

June 7, 2019 at 05:15:53
You still need a router with a VLAN(s) as you still need to get the traffic from the VLAN to the outside world.

I'm guessing you don't typically use VLAN tagging within your environment?

A simple description of your physical network will help. How many switches? Routers?

Typically with VLAN's you have your management VLAN on which all network devices reside.

VLAN 1 = mgmt =

and you might have other VLAN's for other purposes:

VLAN 2 = data =
VLAN 3 = server =
VLAN 4 = VoIP = .4.0/24
VLAN 5 = printers = .5.0/24


VLAN 2 needs to talk to all other VLAN's except 4. 4 does not need to talk to any other VLAN's at all. 3 doesn't need to talk to 4 and 4 definitely does not need to access 3.

All this is done through your firewall rules and/or routing.

Feel free to PM me and we can communicate in a little more depth.

It matters not how straight the gate,
How charged with punishments the scroll,
I am the master of my fate;
I am the captain of my soul.

***William Henley***

Reply ↓  Report •
Related Solutions

Ask Question