signal environment variable in client-disconnect script?

fboliva

Hello guys,

How are you? I hope you are well and safe.

I have been doing a lot of research on the Internet, I have read a lot of documentation (including all OpenVPN documentation) and I would like your opinion, suggestions and help.

I have an OpenVPN server running perfectly and, on that server, I configured the scripts (client-connect and client-disconnect) to write individual files (per user) so that I can quickly find information about connections and solve any problems.

Within the scripts (client-connect and client-disconnect) I use the environment variables to write the user records in csv files ... so far, so good ... but if I need to know the user disconnection reason, I have to look in the openvpn log ... which is not practical at all.

I know that there is a "signal" environment variable and it returns exactly the information I need, but it doesn't work on client-disconnect ... only on the down script.

Is there any way to use this variable in the client-disconnect script, or some other way (or another variable)? If it doesn't exist, don't you think it would be interesting to have this feature - a new environment variable (or even that same "signal" environment variable) that can return this information in the client-connect and client-disconnect scripts?

Thanks in advance!

Best Regards!

TinCanTech

fboliva wrote I know that there is a "signal" environment variable and it returns exactly the information I need, but it doesn't work on client-disconnect ... only on the down script.

The signal variable signifies the reason why the current running openvpn process is exiting or restarting. It has nothing what-so-ever to do with what is happening to the remote peer.

fboliva

The signal variable signifies the reason why the current running openvpn process is exiting or restarting. It has nothing what-so-ever to do with what is happening to the remote peer.

Hello!

Thanks indeed for your reply!

As can be read in openvpn manual:
https://openvpn.net/community-resources/reference-manual-for-openvpn-2-4/

signal
The reason for exit or restart. Can be one of sigusr1, sighup, sigterm, sigint, inactive (controlled by –inactive option), ping-exit (controlled by –ping-exit option), ping-restart (controlled by –ping-restart option),connection-reset (triggered on TCP connection reset), error, or unknown (unknown signal).

Note that signal, in openvpn.log shows detailed info about user/client/remote peer disconnection: SIGTERM[soft,remote-exit] , SIGTERM[soft,inactive], SIGUSR1[soft,ping-restart], etc... so, yes, the variable shows exactly why the remote peer was disconnected.

As I already wrote, an environment variable like signal (or even the signal environment variable itself) that could be used in the client-disconnect script could be useful to return this information within client-disconnect script... I didn't say it has to be exactly that variable, I just mentioned it, stating that it has the information I need (and indeed this environment variable does have that kind of information about the remote peer disconnection).

Best Regards,

TinCanTech

fboliva wrote signal
The reason for exit or restart. Can be one of sigusr1, sighup, sigterm, sigint, inactive (controlled by –inactive option), ping-exit (controlled by –ping-exit option), ping-restart (controlled by –ping-restart option),connection-reset (triggered on TCP connection reset), error, or unknown (unknown signal).

All of which relate to the current running openvpn process not the remote peer.

fboliva wrote Note that signal, in openvpn.log shows detailed info about user/client/remote peer disconnection: SIGTERM[soft,remote-exit] , SIGTERM[soft,inactive], SIGUSR1[soft,ping-restart], etc... so, yes, the variable shows exactly why the remote peer was disconnected.

They may "look" like signal but it is not signal the openvpn variable which relates to the local running process.

I am not saying what you want cannot be done (although, only so much of it can be done) but that is not how it *is* done. There may even be some internal code which is not exposed to the scripts .. but I don't know about that.

No matter what you believe, if you are proposing a change then you will need to discuss that with the devs.

fboliva

Sorry, we encountered an error while displaying this content. If you're a user, please try again later. If you're an administrator, take a look in your Flarum log files for more information.

fboliva

Hi again Friend,

Do not worry! I changed the code (also created a patch), created a new environment variable that reads the signal_string and can be used by the client-disconnect script ... it's working as I needed/suggested it!

Best Regards,

TinCanTech

I look forward to seeing your patch on the mailing list.