How do I find existing client ids

openvpn@jfront.com

If I connect to my server's management port before a client connects, I can discover the client ID from the ">CLIENT:ESTABLISHED,<CID>" message. Later I'm able to use that Client ID for things like tracking bandwidth usage using the " >BYTECOUNT_CLI:<CID>" message.

Is there a way to match client IDs to connections if I miss that initial connection message. E.g., if I connect to the management port after the client has connection, how can I track bandwidth usage?

I've looked at all versions of the status command. This was initially promising, but I don't see any version that includes the Client ID in the output. Is there something I'm missing, or is this just not possible?

TinCanTech

openvpn@jfront.com wroteI've looked at all versions of the status command. This was initially promising, but I don't see any version that includes the Client ID in the output. Is there something I'm missing

status 2 ..

HEADER,CLIENT_LIST,Common Name,Real Address,Virtual Address,Virtual IPv6 Address,Bytes Received,Bytes Sent,Connected Since,Connected Since (time_t),Username,Client ID,Peer ID

:ugeek:

openvpn@jfront.com

Great thanks. I had started writing a question about what version this was in, but then the forum software seems to have crashed. I hope it wasn't because of me -- it seemed to happen right after I pushed the "Full Editor & Preview" button. I won't risk that button this time.

While waiting for this site to come back I looked up the openvpn source. The "Client ID,Peer ID" part was added in commit 1b954192, which doesn't seem to be in any released version. I don't normally use the git command line for diffs against tags, so I might have made a mistake. However it definitely isn't in my version, since v2.3.2 (bundled in Ubuntu 14.04) was from several months before this change.

I've tried a local build (based on the 2.3.2 tarball) with a small patch to add the Client ID. It seems to be working, so I'll probably start running with this locally patched version.

Thanks for the quick help and pointer.

TinCanTech

openvpn@jfront.com wroteit definitely isn't in my version, since v2.3.2 (bundled in Ubuntu 14.04)

That was not clear from your initial post.

openvpn@jfront.com wroteI've tried a local build (based on the 2.3.2 tarball) with a small patch to add the Client ID. It seems to be working, so I'll probably start running with this locally patched version

That is one way but I would think it far better to use:
https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos

openvpn@jfront.com wrote The "Client ID,Peer ID" part was added in commit 1b954192, which doesn't seem to be in any released version

I will double check, you may be right (which means my second comment may not be valid)

openvpn@jfront.com wrotethe forum software seems to have crashed. I hope it wasn't because of me

Probably not you, it crashes very rarely due to an as yet unidentified SQL problem ..

openvpn@jfront.com wroteThanks for the quick help and pointer

You're welcome 8-)

dazo

Beware! Client ID and Peer ID is not the same thing. Peer-ID may point at the same Client-ID , but this link may change during a session's life time. AFAIR, there are no guarantees in the code they will keep a 1:1 relation.

The Client ID field have been present for a long time (pre v2.2 releases, IIRC), and should be available through the 'status' overviews using --status-version 2 or 3. This is available both through the --status dumps or via the TCP based management interface (the status command)

Peer-ID requires both client and server to support this feature, which allows clients to change their public IP address without re-triggering a new key exchange. Peer-ID client side support first arrived in v2.3.6, with several bug fixes arriving in v2.3.7. The server side Peer-ID support will arrive in v2.4 (currently in git master).

[edited, clarified a few details]