1. 26 Jan, 2022 1 commit
  2. 24 Jan, 2022 1 commit
    • Martin Matějek's avatar
      Do not activate client right after adding config · a7f008be
      Martin Matějek authored
      Currently new openvpn client connection is marked as enabled and
      immediately started after adding (after openvpn restart).
      
      This can be quite dangerous, because enabling and starting new vpn
      connection could mess up already running vpn connections or make router
      inaccessible in certain circumstances, without simple way to disable
      such vpn client.
      
      Mark new vpn client as disabled after adding and force user to activate
      it in additional separate action.
      
      closes: #20
      a7f008be
  3. 21 Jan, 2022 1 commit
  4. 05 Aug, 2021 1 commit
  5. 04 Dec, 2020 2 commits
    • Martin Matějek's avatar
      version 0.5.1 · 687c09f5
      Martin Matějek authored
      687c09f5
    • Martin Matějek's avatar
      Force firewall reload after adding new vpn client · e02f8436
      Martin Matějek authored
      Traffic via newly added client won't pass through until firewall is reloaded.
      Unfortunately it isn't triggered by network restart, so we have to make sure it happens.
      
      Reloading firewall after removal of client on the other hand
      seems to work fine most of the time, but still it isn't triggered by network restart reliably.
      So this will force reload after removing vpn client as well.
      e02f8436
  6. 10 Nov, 2020 5 commits
  7. 06 Nov, 2020 1 commit
  8. 06 Oct, 2020 2 commits
  9. 21 Aug, 2020 1 commit
  10. 03 Jul, 2020 1 commit
  11. 11 Jun, 2020 1 commit
  12. 03 Jun, 2020 1 commit
  13. 12 Nov, 2019 1 commit
  14. 09 Oct, 2019 4 commits
  15. 08 Oct, 2019 1 commit
  16. 02 Oct, 2019 2 commits
  17. 22 Aug, 2019 2 commits
  18. 21 Aug, 2019 1 commit