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
Hi @brandonros, good question! The difference is related to how WireGuard stores data vs. how WS4W stores data.
In WireGuard, each peer's config file contains info about itself as well as info about the peer(s) it's connecting to. However, in the UI, I restructured things to make it easier to configure. You'll notice that all of the server configuration is one place and all of the client configuration is in another place. Ultimately, bits and pieces of that data is spread between the server and client config files. The data directory contains all of the info for a given entity as WS4W sees, and the wg directory contains the same data, divided up into the correct files for WireGuard to understand it.
In terms of where "Open client configuration directory" brings you, I agree it would make sense to go right into the wg directory. I will see if there was any technical reason why it didn't do that.
It's a little confusing as a user to have the same .conf files in 2 different directories. When I click this:
I expect to be brought right to the directory needed to copy
.conf
files to clients.You want the .conf from
clients_wg
and notclients_data
when it comes toqrencode
/ sharing with other devices.The text was updated successfully, but these errors were encountered: