I am attempting to create separate Virtual Networks each with address ranges in two separate networks i.e. 10.8.8.128 – 10.8.8.252 and 10.10.10.128 – 10.10.10.252. The underlying bridge of my host is defined with 10.8.8.0/24; Gateway of 10.8.8.1. I’m assuming what I want to achieve is possible since it states in the Operations Guide under Virtual Network Tips “ARs do not need to be of the same type or belong to the same IP network”.
My first virtual network:
NAME: vnetwork1
USER: oneadmin
GROUP: oneadmin
CLUSTERS: 0
BRIDGE: virbr0
VN_MAD: dummy
VIRTUAL NETWORK TEMPLATE
BRIDGE="virbr0"
DNS="8.8.8.8, 8.8.4.4"
GATEWAY=“10.8.8.1"
PHYDEV=”"
SECURITY_GROUPS=“0"
VLAN_ID=”"
VN_MAD="dummy
My second virtual network:
NAME: vnetwork2
USER: oneadmin
GROUP: oneadmin
CLUSTERS: 0
BRIDGE: virbr0
VN_MAD: dummy
USED LEASES: 1
VIRTUAL NETWORK TEMPLATE
BRIDGE="virbr0"
DNS="8.8.8.8, 8.8.4.4"
GATEWAY="10.10.0.1"
NETWORK_ADDRESS="10.10.0.0"
NETWORK_MASK=“255.255.255.0"
PHYDEV=”"
SECURITY_GROUPS=“0"
VLAN_ID=”"
VN_MAD=“dummy”
vnetwork1 works perfectly as expected when associated with a VM. But vnetwork2 does not work at all . . . i.e. I cannot ping the VM associated with vnetwork2 from the host and when I VNC into the VM I cannot ping the host (destination host unreachable).
So my question . . . Am I misinterpreting what is stated in the Operations Guide? If not, any thoughts of what I’m missing? Do I need to define additional routing on the host?