Hello.
Netstat is only counting traffic sent or received on the interface; e.g.
the tunnelled bytes themselves, as it should. WireGuard however is
counting that, plus all of the encapsulation overhead (header, MAC,
etc), plus packets not sending or receiving tunnelled data (for example,
keep-alive
Hi,
I use the Wireguard Go C API to integrate with my packet tunnel network
extension to forward traffic to the WG tunnel on Mac OS. I also use the
wgGetConfig() API to get tunnel status information.
During my testing, I noticed some differences between what the netstat -ib
reports and what Wi
