-
Notifications
You must be signed in to change notification settings - Fork 18
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
Feature Request: wireguard-ui option #66
Comments
hi i would really like this too, im pretty good with command line but if i have to remote in with my phone to setup a new client so i can connect a new laptop having a ui would be much nicer. in the mean time @CaptInsano could you explain how you installed it on the UDM? is it just a matter of extracting the tar file to /mnt/data? edit: nvm i got it working. as for running |
My solution (very janky) includes a solution for running I would really really appreciate any advice on making my solution better and conform to best practice as I am aware how janky it is!! My steps: Create working Dir
Gather wireguard-ui binary and make executable
Gather a busybox binary with notifyd enabled (built-in version does not support inotify) (This is an older version of busybox here but available online, would love if someone could offer better solution)
Create a script to restart wireguard which will be called on wg0.conf config changes made my wireguard-ui:
contents of restart_wg:
make executable:
Create on.boot.d script to start wireguard-ui and watch for config changes, restarting wireguard as needed
contents of wireguard-ui.sh (note I also use this script to start my instance of wireguard on boot and is set to run after 10-setup_wireguard.sh)
make executable:
Finally run it and things should be up and running!
|
oh cool thanks |
do you have an issue with the ui loosing its db when the UDM reboots? |
I do not have this issue but maybe I have a typo in the instructions I provided. wireguard-ui makes a db folder wherever the wireguard-ui command is made from, this is why my script moves to the /mnt/data/wireguard-ui folder before issuing the wireguard-ui command. my "mnt/data/wireguard-ui" folder contains the following:
and if I killall wireguard-ui instances (killall -9 wireguard-ui) and then just run the "/etc/data/on.boot.d/20-wireguard-ui.sh" command (simulating a reboot) it comes back up and works for me. |
oh i compleatly missed the cd command. thanks |
I need beta-testers for my repo. Wireguard-ui is included there. Requirements: UDM base or pro, firmware at least on 2.4.x (fully tested on my UDM base 2.5.x). see here. Start with this commandline (save your wg0.conf if something happens)
then
|
I know this is a big ask and possibly against the minimal ideals of this project but would you ever consider adding an option to include wireguard-ui with this project?:
https://github.com/ngoduykhanh/wireguard-ui
They have an ARM64 binary in their releases that runs on the UDM that facilitates a much easier setup for those of us who do not always find it easiest in the commandline or ssh terminal. Also makes it so easy to add new clients and scan qrcodes via other devices.
I am currently running the https://github.com/ngoduykhanh/wireguard-ui/releases/download/v0.3.7/wireguard-ui-v0.3.7-linux-arm64.tar.gz binary in a very hacky way by adding:
nohup ./wireguard-ui &
to my setup_wireguard.sh in the on_boot.d folder.
The current issue is that it requires a manual issuing of the "wg-quick down wg0" and "wg-quick up wg0" commands after any configuration changes but the project repo README.md suggests ways to automate that which is above my very minimal ability!
Again, I appreciate that this may not be in the interests of the dev but I felt it was worth asking!!
Thanks again
The text was updated successfully, but these errors were encountered: