id summary reporter owner description type status priority milestone component version severity resolution keywords cc 1434 Client-disconnect script env does not have common_name tct "Under certain circumstances, `--client-disconnect` has the wrong value for `common_name` in the `env`. In this case `--username-as-common-name` is in use and `username` is not the same as `common_name`. Follow-up to #160 #1370 Possibly Related to: #167 What actually takes place is as follows: 1. Client connects normally - UDP - `username` is assigned to `common_name` 2. Client renegotiates normally. 3. Client disconnects normally. This leads the server supplying `common_name` not `username` to `--client-disconnect`, every time. I ran a single standard server and a single standard client. I used a simple script to monotonically dis/enable routing to the server, over a period of 10mins. The client uses `--reneg-sec 270`, so the client has always done a renegotiate when the routing becomes disabled. Then the server does `--ping-timeout` for the client. Then the server runs `--client-disconnect` with the wrong value for `common_name`, every time. The server ran for ~20 hours and generated this error 130 times." Bug / Defect closed major release 2.5.5 Generic / unclassified OpenVPN git master branch (Community Ed) Not set (select this one, unless your'e a OpenVPN developer) fixed