-
-
Notifications
You must be signed in to change notification settings - Fork 33
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
support for Pre/Post Up/Down scripts #94
Comments
Sounds good to me. @DasSkelett @GoliathLabs |
What additional routes would you like to add? If you want to route additional prefixes to the clients, that would require adding them to |
@DasSkelett one of the peers is a raspberry pi on my home network that acts as a router. I am pushing a route to that network via its wireguard IP, so that I can reach devices on my network that do not support wireguard |
While I'm not sure whether your described setup would work like this, it looks like there is indeed some demand for arbitrary code execution on interface up/down. |
It will need a permission check of the config file, the application should at least block the execution of the custom commands if it is not owned by |
First of all great project!
I am wondering if there is an interest in supporting Pre/Post Up/Down scripts. I have implemented something similar in another wireguard management project here: naggie/dsnet@e782db3
wg-access-server is already doing the iptables setup yet there is still a case where that could be useful. I am using a PostUp command to add additional routes on the wireguard interface and would like to do that with wg-access-server too. There are probably other use-cases. LMK if that is a desired feature and I will send a PR.
The text was updated successfully, but these errors were encountered: