VPN - Client-to-Site using OpenVPN protocol - Omada Software Controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello,
I just got some new products from TP-link, that I would love to use together with the Omada Software Controller.
My setup is:
ER605 (Gateway) -> TL-SG3428MP (switch) -> EAP620 (APs)
My needs are pretty simple, I have to create 2 wireless networks for my office:
SSID: Office
SSID: Office_VPN
The Office_VPN traffic should go through our OpenVPN server (hosted somewhere in this world), but there's a catch, the Open VPN server is configured to allow traffic just through ports 80 and 443.
All the switch ports settings are default, trunk.
The Wireless Networks configuration looks like:
And those are the interfaces,
And for sure the Client-to-Site, ovpn configuration,
Both wireless networks send the traffic out to the world on ports 80/443 just fine, but the problem is that I could not send any traffic through the rest of the ports (e.g. 22), no matter what Wireless Network I'm using. Any advice?
I've expected that only the Office_VPN network that forwards traffic through the OpenVPN to have the ports locked.
Thank you,
Tudor
Thank you Virgo, I do have 2 WAN connections and did try to use the policy routing in order to mitigate this issue. The result is that, once I enable the routing policies for the VPN IP group, the VPN connection is interrupted. Also, I tried to associate a WAN port to a specific VLAN, no luck so far. (see the attached image)
