Hey guys,
I have an ESXi lab with "All in One" style setup. Since it is a test/dev lab, it is designed to be non-critical to the rest of the home LAN. PCs have Firewall,DHCP,DNS,etc served up by a small DDWRT-based wireless router device which has all routes from the ESXi network configured. So a PC at 192.168.1.100 can access a guest under ESXi at 10.0.0.100, for example.
Comments, criticisms? I am also very interested to introduce VLAN'ing but for some reason it's a difficult concept for me.
The ESXi server itself is sort of like it's own network within itself. It has (4) virtual switches configured:
I have an ESXi lab with "All in One" style setup. Since it is a test/dev lab, it is designed to be non-critical to the rest of the home LAN. PCs have Firewall,DHCP,DNS,etc served up by a small DDWRT-based wireless router device which has all routes from the ESXi network configured. So a PC at 192.168.1.100 can access a guest under ESXi at 10.0.0.100, for example.
Comments, criticisms? I am also very interested to introduce VLAN'ing but for some reason it's a difficult concept for me.
The ESXi server itself is sort of like it's own network within itself. It has (4) virtual switches configured:
- WAN: pfSense is the only VM connected to WAN. VMkernel management is also on this switch. It is also the only vSwitch with actual physical NICs.
- LAN: Network segment where all non-internet facing VM guests are connected to. Gateway is pfSense
- DMZ: Network segment where all internet facing VM guests are connected to. Gateway is pfSense
- Storage: VMkernel NFS storage connects to a virtualized NAS server. No gateway on this net
Last edited: