Omada VPN Routes
I have a VMWare cloud hosted site that I am attempting to use a ER8411 to create a manual IP Sec VPN tunnel to. VMWare and the Omada OC200 controler shows the VPN has been established. I have paired the VPN connection to a VLAN that is not VLAN1 on the Omada network. With a laptop on that VLAN, Im unable to connect or ping anything on the VMWare site. I have duplicated all the other firewall settings in VMWare similar to my other site to site links, generated with SonicWall routers. When I print the routing table on the laptop I do not see the VMWare LAN IP range. When I look in the OC200 controller, outside of the VPN connection settings, I see no routes or ACLs created for the connection. How does the controller tell the VPN router how to route the traffic without this? Is it not working properly because VLAN1 is not included? I do not wish to include VLAN1 traffic in the VPN connection.