* As you may or may not be aware of, WireGuard was built with the necessity to know the user's (your) IP address (also known as source IP address) and maps it to an internal IP address.
* WeVPN deployment of WireGuard disables logs by running it in "blind_operator_mode" meaning that the operating system itself does not allow for logging to JournalCTL or for sniffing packets even if you are on the server. Trying to do something like "tcpdump" for example on the network interface for wg, it will result in a response of "you don't have permission to capture on that device"
* This leaves the only true way to capture any "logs" or "information" by somehow capturing memory and translating the memory in ASCII and hopefully getting something useful there?
* Essentially there is no logging for WireGuard - the process runs isolated and in a black-box type environment