LTE devices "Non-OpenVPN client protocol detected"

[njmatt415]

I'm testing an OpenVPN client baked into LTE devices. Both devices show the same error in the OpenVPN access server v2.11 logs, so it's not an isolated issue. Can someone tell me what this means? Google is no help.

2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: '2024-02-03 17:48:08 Note: OpenSSL hardware crypto engine functionality is not available'
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 tls-crypt-v2 server key: Cipher 'AES-256-CTR' initialized with 256 bit key"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: "2024-02-03 17:48:08 tls-crypt-v2 server key: Using 256 bit message hash 'SHA256' for HMAC authentication"
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: '2024-02-03 17:48:08 TCP connection established with [AF_INET]xxx:55546'
2024-02-03T17:48:08+0000 [stdout#info] [OVPN 0] OUT: '2024-02-03 17:48:08 Socket flags: TCP_NODELAY=1 succeeded'
2024-02-03T17:48:10+0000 [stdout#info] [OVPN 0] OUT: '2024-02-03 17:48:10 xxx:55546 Non-OpenVPN client protocol detected'
2024-02-03T17:48:10+0000 [stdout#info] [OVPN 0] OUT: '2024-02-03 17:48:10 xxx:55546 SIGTERM[soft,port-share-redirect] received, client-instance exiting'

[openvpn_inc]

Hello njmatt415,

I think you're focusing on the wrong message. Access Server shares its TCP port for VPN connections with its web interface. If a web browser connects to that TCP port, that's logged as a non-openvpn client protocol. Seems perfectly normal. For the rest of the messages, seems like the connection is working. I do see a lack of hardware support for cryptographic operations but that's not a dealbreaker, just means things could be slower than they can be.

So things look fine. What is actually not working? Does the client say it is not connected? Can you not ping anything over it? Are you doing any kind of tests like packet capturing and ping tests and such to determine if the packets actually make it to the other side or not? I would first see if the client connection is established and work from there.

Kind regards,
Johan