OpenVPN TLS Renegotiation Time Storage

[TonyK132]

Does anyone know where the TLS Renegotiation Time value is stored, and if it generates a CRON job, where that setting is located? I had a problem with my VPN (I use PIA) that whenever the Regeneration Time occurred, it would interrupt my streaming audio. No browser that I tried (FF, Vivaldi, Brave, Chrome) could deal with the discontinuity in the VPN stream, so I increased the time to happen once/day, but I would like the Renegotiation Time to occur at 4am when I do not care about an interruption in the streaming audio. Alternately I could wake up at 4am, and cause a change to the VPN screen that would (presumably) cause that Time to reset to once/day at 4am. But I would like a procedure that is more definitive.

 

[ColinTaylor]

The renegotiation time is a duration not a time of day. Why not set it to zero if it's a problem? Alternatively, if you need the duration to start at a particular time you could create a cron job that restarts the client.

 

[TonyK132]

The renegotiation time is a duration not a time of day. Why not set it to zero if it's a problem? Alternatively, if you need the duration to start at a particular time you could create a cron job that restarts the client.

Yes, a duration. But I'm guessing it creates its own cron job, which is exactly what I'm looking for. But I like the idea of a duration of zero, which I guess means Never. What would be the commands that I would give it with my cron job, presumably to stop then restart it?

 

[TonyK132]

Another hint as to what's going on. I came to my PC at around 21:40, and saw that the streaming stopped. Don't know when it stopped, but I did find this this crash info in the logs. Does this mean anything to anyone?

Dec 22 18:57:45 RT-AC86U-1BD0 kernel: Hardware name: Broadcom-v8A (DT)
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: task: ffffffc010cf4b40 ti: ffffffc0091dc000 task.ti: ffffffc0091dc000
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: PC is at 0xf71879cc
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: LR is at 0xf72c4ee0
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: pc : [<00000000f71879cc>] lr : [<00000000f72c4ee0>] pstate: 60070010
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: sp : 00000000ffbe95b8
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x12: 00000000f7306b38
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x11: 000000000002889c x10: 0000000000028458
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x9 : 00000000000175e9 x8 : 00000000000288a0
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x7 : 0000000000000018 x6 : 00000000f77046d0
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x5 : 0000000000000004 x4 : 0000000000000000
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x3 : 0000000000000010 x2 : 0000000000000001
Dec 22 18:57:45 RT-AC86U-1BD0 kernel: x1 : 0000000000000000 x0 : 0000000000000000

 

[RMerlin]

Yes, a duration. But I'm guessing it creates its own cron job

No. It's all handled internally by openvpn.

 

[TonyK132]

What OpenVPN command or commands can I use to cause a TLS Renegotiation to happen? I'm thinking I would put that into an executable script, and cron it to happen at 4am.

 

[ColinTaylor]

As Merlin said, it's handled internally by OpenVPN. So you'd need to restart the client connection.

killall -s SIGHUP vpnclient1

or

service restart_vpnclient1

 

[TonyK132]

As Merlin said, it's handled internally by OpenVPN. So you'd need to restart the client connection.

killall -s SIGHUP vpnclient1

or

service restart_vpnclient1

Thanks, that's what I was looking for.
What's handled by OpenVPN is a duration until the next renegotiation. Doing a cron lets me set it to a specific time.