config is in /etc/openvpn/server.conf

most time is updating routing

In init script there's no case for reload. "service openvpn restart" is just stop and then start the process, which obviously will kick everybody off

  • 1
    Will it kick everybody off? Not sure that is true. – dmourati Jan 16 '16 at 5:21
  • dmourati, you can try. Once you reload the connections will be terminated immediately from server end. – Carl Jan 18 '16 at 1:43
  • 4
    From the OpenVPN manual page: SIGHUP Cause OpenVPN to close all TUN/TAP and network connections, restart, re-read the configuration file (if any), and reopen TUN/TAP and network connections. – FlogFR Sep 12 '17 at 7:04
  • Did you ever get this figured out? – emmdee Apr 23 '18 at 23:25

If you need to propagate new routes to the connected clients, you had to kick off anybody and let them reconnect, as routes are pushed only after connection establishment.

| improve this answer | |
  • 7
    update routing is just one scenario, and it does not need to push new routes to everyone immediately, it can happen when clients reconnect next time, but the server need to load new configuration. – Carl Jan 18 '16 at 1:44
  • 1
    doesn't really answer the question. – Daniel Farrell Jan 9 at 22:25

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.