You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
now the script will generate the first client's config file like wg0-client-2.conf in root's home.
in my sceranio , I would like to rename the file to match user's name and devices
like wg0-client-eric-iphone8.conf
but if I do the rename , then next time when I generate another client , the script will not be able to determine client's ip address and then create wg0-client-2.conf again.
so if I want to use the script to keep generating config without modify client's ip address , then I will not be able to rename the config file.
then , how about add a "comment" in script's interactive process , and just add the comment into config file , so at least I can use grep to find out user's config ?
and also I think that is not proper to store config files in root's home directory , maybe it should be a customize variable ?
The text was updated successfully, but these errors were encountered:
You can rename wg0-client-2-conf to wg0-client*, where * can be whatever you want. Subsequent client generations will have their config filenames incrementally increased. Line 15 of setup.sh is responsible for this:
I can look into the comment capabilities. Storing config elsewhere could be possible, but it becomes a breaking change for users, if they upgrade. It also opens up the possibility that people may scatter the config files around their system. A suitable option would be to drop them into a new directory under /etc/wireguard/clients?
now the script will generate the first client's config file like wg0-client-2.conf in root's home.
in my sceranio , I would like to rename the file to match user's name and devices
like wg0-client-eric-iphone8.conf
but if I do the rename , then next time when I generate another client , the script will not be able to determine client's ip address and then create wg0-client-2.conf again.
so if I want to use the script to keep generating config without modify client's ip address , then I will not be able to rename the config file.
then , how about add a "comment" in script's interactive process , and just add the comment into config file , so at least I can use grep to find out user's config ?
and also I think that is not proper to store config files in root's home directory , maybe it should be a customize variable ?
The text was updated successfully, but these errors were encountered: