Hi all,
did i get that right that no logging is available atm on IPFire for WG?
that’s really a showstopper in my Opinion ^^
If so, is it planned to have Logfiles just as IPSec & OVPN?
WireGuard simply does not log anything.
The article that you have linked is adding debugging information. That is useful for developers, but not for administration of WireGuard tunnels.
So, this is not a showstopper. It is just how WireGuard operates. If you want more logging, you can change to use IPsec or OpenVPN. All other WireGuard implementations will behave exactly the same as this is not an IPFire design choice.
Because it isn’t possible to realise this, this is not a planned feature.
3 Likes
Thx for the clarification!
I just like to see what’s going on - so this is definitely a ‘showstopper for me’ 
Since I don’t see any advantages for myself compared to OVPN Roadwarrior, I have deactivated Wireguard again 
Hi @luxskywalker ,
what is it you want to achieve or what do you need?
Depending on the Firewall Ruleset and Logging of these Rules you could get a pretty good overview about the Wireguard activities. If you want to know how often and from where your Peers/Roadwarriors connect, you may achieve this with a DNAT-Rule. Change the WG-Port, maybe to UDP 51821, but let the Peers connect to 51820 anyway. Forward 51820 to 51821 and turn on logging. This way you will get a log about all incoming connections and their source. Via the logging of other Rules, maybe one that allows your Peers HTTPS to RED, you will see all activities and can even filter by Country. Just as you can filter “green0” or “blue0” as Country you can filter “wg0” and get some kind of summary about just the Wireguard connections.
I wonder if the Who Is Online Plugin (WIO) could give you another option.
1 Like
That’s a great idea, thank you!
I actually just want to monitor who tries to connect, when and how often.
I now run many Services from home - so I have to regularly check what’s going on