Hi,
I Have the following networks.
WiFi Network:
Windows WiFi (192.168.1.21/24)
Windows WiFi Router connected to internet (192.168.1.254)
Dell Network
Windows Laptop LAN (192.168.10.1/24)
Dell Server (192.168.10.10/24)
ESXi Server (192.168.10.15/24)
The Dell Server is connected directly to the laptop via Ethernet Cable. From my laptop I can ping Dell and ESXi installed on the Dell Server, and vice-versa. I want to route traffic from the 192.168.10.0/24 network (LAN) to 192.168.1.0/24 network (WiFi). Can the Windows Route Command be used for this purpose, is it possible ?!. The following is my Routing Table.
IPv4 Route Table
Active Routes:
Network Destination | Netmask | Gateway | Interface |
0.0.0.0 | 0.0.0.0 | 192.168.1.254 | 192.168.1.21 |
0.0.0.0 | 0.0.0.0 | On-link | 192.168.10.1 |
0.0.0.0 | 0.0.0.0 | 192.168.10.1 | 192.168.10.1 |
127.0.0.0 | 255.0.0.0 | On-link | 127.0.0.1 |
127.0.0.1 | 255.255.255.255 | On-link | 127.0.0.1 |
127.255.255.255 | 255.255.255.255 | On-link | 127.0.0.1 |
192.168.1.0 | 255.255.255.0 | On-link | 192.168.1.21 |
192.168.1.0 | 255.255.255.0 | On-link | 192.168.10.1 |
192.168.1.0 | 255.255.255.0 | 192.168.10.2 | 192.168.10.1 |
192.168.1.21 | 255.255.255.255 | On-link | 192.168.1.21 |
192.168.1.255 | 255.255.255.255 | On-link | 192.168.1.21 |
192.168.1.255 | 255.255.255.255 | On-link | 192.168.10.1 |
192.168.10.0 | 255.255.255.0 | On-link | 192.168.1.21 |
192.168.10.0 | 255.255.255.0 | On-link | 192.168.10.1 |
192.168.10.1 | 255.255.255.255 | On-link | 192.168.10.1 |
192.168.10.255 | 255.255.255.255 | On-link | 192.168.1.21 |
192.168.10.255 | 255.255.255.255 | On-link | 192.168.10.1 |
224.0.0.0 | 240.0.0.0 | On-link | 127.0.0.1 |
224.0.0.0 | 240.0.0.0 | On-link | 192.168.1.21 |
224.0.0.0 | 240.0.0.0 | On-link | 192.168.10.1 |
255.255.255.255 | 255.255.255.255 | On-link | 127.0.0.1 |
255.255.255.255 | 255.255.255.255 | On-link | 192.168.1.21 |
255.255.255.255 | 255.255.255.255 | On-link | 192.168.10.1 |
Persistent Routes:
Network Address | Netmask | Gateway Address |
192.168.1.0 | 255.255.255.0 | 192.168.10.1 |
192.168.10.0 | 255.255.255.0 | 192.168.1.21 |
0.0.0.0 | 0.0.0.0 | 192.168.10.1 Default |
I got this working as follows in case someone else has limited resources for home lab.
This was done by Bridging my laptop's LAN and VMware Workstation's Host-Only adapter (vmnet6) in Windows Control Panel.
The IP address of the Bridged adapter was set in 192.168.10.0/24 network, and this adapter was connected as a port in a Firewall VM in VMware workstation from where I was able to route traffic to any required subnet, be it WAN or any other network.
Laptop LAN Network - 192.168.10.0/24
VMware Host-Only adapter (vmnet6) Network - 192.168.111.0/24
Bridged IP Network - 192.168.10.0/24 (in my case 192.168.10.1/24)
Firewall VM in VMware Workstation on vmnet6 Host-Only adapter IP - 192.168.10.4 (this was also set as the Gateway for both Dell and ESXi. This Firewall VM was set with rules to direct traffic to where needed. And as the Firewall VM had WAN (VMware Workstation NAT) traffic was also able to go out to the internet.
https://i.ibb.co/2sLXF3z/Bridged-NIC.png
https://i.ibb.co/2STBqbc/Bridged-NIC-IP.png
https://i.ibb.co/DkvPL63/Bridged-NIC-Properties.png
https://i.ibb.co/wLPvj4y/vmnet6.png
Now my ESXi, Dell both can communicate with VMs in my Laptop's VMware Workstation.
I got this working as follows in case someone else has limited resources for home lab.
This was done by Bridging my laptop's LAN and VMware Workstation's Host-Only adapter (vmnet6) in Windows Control Panel.
The IP address of the Bridged adapter was set in 192.168.10.0/24 network, and this adapter was connected as a port in a Firewall VM in VMware workstation from where I was able to route traffic to any required subnet, be it WAN or any other network.
Laptop LAN Network - 192.168.10.0/24
VMware Host-Only adapter (vmnet6) Network - 192.168.111.0/24
Bridged IP Network - 192.168.10.0/24 (in my case 192.168.10.1/24)
Firewall VM in VMware Workstation on vmnet6 Host-Only adapter IP - 192.168.10.4 (this was also set as the Gateway for both Dell and ESXi. This Firewall VM was set with rules to direct traffic to where needed. And as the Firewall VM had WAN (VMware Workstation NAT) traffic was also able to go out to the internet.
https://i.ibb.co/2sLXF3z/Bridged-NIC.png
https://i.ibb.co/2STBqbc/Bridged-NIC-IP.png
https://i.ibb.co/DkvPL63/Bridged-NIC-Properties.png
https://i.ibb.co/wLPvj4y/vmnet6.png
Now my ESXi, Dell both can communicate with VMs in my Laptop's VMware Workstation.