the vsphere box is plugged into the network 11.9.32.0/24, and has an IP of 11.9.32.17 (i.e. thats the ip we type into the vsphere client). this network is the DMZ, so is directly behind the firewall (which is also the default gateway and router, and has an ip of 11.9.32.2).
If we create VMs, and give them an IP on the same network, eg 11.9.32.18, then we can see them and it works.
However, we have many VMs we want to setup, and we want to put them on a separate network, e.g. 11.9.52.0/24
I cant see anywhere to set this up in vsphere. Do we need to create VMs to act as routers? Or does VSphere have any routing ability?
The host has 4 nics, but as we only have one network, only one nic is connected (with the ip of 11.9.32.17).
Our FW does not support multihoming on the LAN port (its pfsense, unfortunately), so we cant add another VLAN/subnet on the physical switch, and multihome the vsphere nic.
vsphere virtual switches are strange beastes - they seem to do some routing themselves. We dont fully understand how they work.
however, if we give a VM an ip of say 11.9.52.20, and have it connected to our only vswitch which is connected to our only NIC, it does not work, i.e. the switch/vsphere do not magially do routing.
We setup a route in our default gateway for 11.9.52.0/23 to go to 11.9.32.17.
If I ping 11.9.52.anything, it gives:
[root@host15 ~]# ping 11.9.52.233
PING 11.9.52.233 (11.9.52.233) 56(84) bytes of data.
From 11.9.32.2: icmp_seq=1 Redirect Host(New nexthop: 11.9.32.17)
So looks like the static route is working up to the vsphere box, but how do you configure static routes in vsphere?
Under configuration/neworking, we have just one standards switch, with teh working vms (with 11.9.32.x) and the non working vms (11.9.52.x) and the single physical adpater.