Firmware Release for OpenVPN WAN

[georgeeo]

What version of the OpenVPN client does this WAN license install? Specifically, I’m wondering if it supports Data Channel Offload as stated here:

The client does not need to use DCO to connect to a server that uses DCO. With only one side doing DCO, there is already a performance benefit. However, it is best if both sides use it. The following clients can use DCO on the client side, although it will have to be enabled separately in the client.

Clients with DCO capability:

• OpenVPN3 Connect for Windows (as of 3.4.0).
• OpenVPN3 Linux client (check with the community documentation for the supported Linux operating systems).
• OpenVPN 2.6.0 or newer (check with the community documentation for the supported Linux operating systems).
• OpenVPN GUI community client for Windows (refer to community downloads).

[shmoesolid]

I am having this same issue currently. I have an OpenVPN Access Server that it is setup to connect to. Our Cradlepoints properly share their client network with the server, but this Peplink absolutely refuses to route traffic to the client network no matter the combinations I’ve tried. Configurations are no different.

I will be back on-site tomorrow to investigate further, but currently devices on the client network can reach the server, but the server cannot reach the client network, only the tunnel network. Firmware on the Peplink is upgraded.

[jgsieve]

please share tracert and provide your existing defined static routes.