# OpenVPN keepalive parameter in configuration

**URL:** <https://community.ipfire.org/t/openvpn-keepalive-parameter-in-configuration/8189>\
**Category:** OpenVPN\
**Created:** [1 July 2022 12:32 UTC](https://community.ipfire.org/t/openvpn-keepalive-parameter-in-configuration/8189 "2022-07-01T12:32:36Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pmueller](https://community.ipfire.org/user_avatar/community.ipfire.org/pmueller/32/9019_2.png) [@pmueller](https://community.ipfire.org/u/pmueller)\
**Post date:** [5 July 2022 14:56 UTC](https://community.ipfire.org/t/openvpn-keepalive-parameter-in-configuration/8189/2 "2022-07-05T14:56:49Z")

</div>

Hi,

thank you for reporting this.

As far as I understand, this is not an issue related to 2FA, so I moved it into a new thread to keep the original one concise.

To the best of my understanding, however, this is like it is expected to work: If keep-alive is configured, the appropriate directives will make their way to the configuration files, if not, they are not there. In the latter case, OpenVPN connections will just eventually time out - a keep-alive usage is certainly the more robust way.

Perhaps we should enable it by default? I don’t really see any disadvantages of that…

Thanks, and best regards,  
Peter Müller

---

_[View the full topic](https://community.ipfire.org/t/openvpn-keepalive-parameter-in-configuration/8189)._
