Cross Vlan Access Stopped when 3rd party VPN Application Started - ER605 - OC200 - TL-SG2008P
( Why does this forum force picking a product that is not in scope of subject matter ? )
I want to use Omada OpenVPN client to connect to my ( paid subscription based ) NordVPN OpenVPN server - however it requires a user name and password - which means that it will not connect . So, I have tried using the NordVPN client and 2 other clients while adminstrating Omada SDN and I find that when I connect to the server ( no matter what protocol ) they stop my subnet access between vlans .
I have the OC200 on native LAN at 192.168.22.x and TL-SG2008P on vlan ' main ' at 192.168.44.x - my desktop PC is on vlan ' main ' .
Ordinarily from my desktop, I am able to ping the OC200 and access the controller via web browser and adminstrate operations . ( Without ACL )
However, if I start up a separate stand-alone VPN client - such as NordVPN - or either of two other OpenVPN clients, suddenly I am not able to access the OC200 .
I have tried setting a Switch ACL from IP Group to IP Group and it does not solve the problem .
IP Groups : desktop 192.168.44.77/32 to OC200 168.22.55/32 .
No problem with access until I run the separate VPN client . Does not matter what protocol the client is using or which program used of the 3 that I have .
That seems very strange that running a separate VPN would affect connectivity on SDN .
Any suggestion of how to regain access while VPN is running ?
I also have a question about being able to have a user name and password using the ER605 client VPN . I will put that in another thread .