-
-
Notifications
You must be signed in to change notification settings - Fork 42
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problem: Unable to assign a Wireguard instance to peer #150
Comments
I was not able to reproduce the issue.
Please review the examples and provide the Ansible-Tasks & -Config if the issue still is present. |
Currently, the process to create a Wireguard peer and server is done like this:
However I feel this is not the optimal way to do it... IMHO, the wireguard sever and peer creation should be done this way:
But currently, there isn't any field in My proposition would be to create a wireguard peer (after the wireguard server creation) with something like this: - name: Adding peer
ansibleguy.opnsense.wireguard_peer:
name: 'test1'
endpoint: 'wg.template.ansibleguy.net'
allowed_ips: ['10.200.0.1/32']
public_key: 'gTuhGXA28/qRSLPnH3szr2+A4l3C4tKlUsOORV63+SE='
server: 'test1' |
You are right. Feel free to test the new implementation on the latest version and report back if you find an issue with it: |
Modules
ansibleguy.opnsense.wireguard_peer
Version
Ansible Version
OPNSense Version
OPNSense-Plugin Version
Issue
The module does not allow to assign the current peer to a Wireguard instance.
There should be an
instance
parameter of this module to allow to create a peer and associate it to an instance.Config Ansible
Config OPNSense
Debug Output
Profiling Output
The text was updated successfully, but these errors were encountered: