softasap / sa-vpn-softether Goto Github PK

Every time I run Ansible the VPN server gets reconfigured, and that means new certificate.
New certificate means that all clients need to be reconfigured as well. Is there a way to stop this behaviour? And preferably, reconfigure the server if there were deviations in configuration, but not generate a new certificate?

One option missing for this role is to update PATH environment with {{softether_home}}

personally i have added this small task to do this

- name: "add {{softether_home}} to path"
  lineinfile:
    dest: /etc/profile.d/softether.sh
    state: present
    create: yes
    regexp: '^export PATH'
    line: 'export PATH=$PATH:{{softether_home}}'

due to use of apt module & specifiic command for ubuntu, this roles only work on ubuntu/debian machine

Hi,

I have modify the templates/scenarios/create_hub to eventually set a administrator password :

{% if softether_master_password is defined %}
ServerPasswordSet {{softether_master_password}}
{% endif %}

It's working well on the first deployment

But it's failed on next deployment on task "Proceed with setup"
as it's type ./vpncmd localhost /server /IN:{{softether_init_script}}
and it's should be :
./vpncmd localhost /server /IN:{{softether_init_script}} /PASSWORD:{{softether_master_password|default("")}}
( with the |default("") it's also working when it's not set a password

my temporary workarround is to stop the service before deploy
but it's not a fix ...

We can replace then " - name: SoftEther | Proceed with setup"
with

shell: ./vpncmd localhost /server /IN:{{softether_init_script}} /PASSWORD:{{softether_master_password|default("")}}

but it's will failed on the first deployment as it's not yet a password set

So i'm not sure how we can handle it ...
a idea ?