* Log debug packets
@ 2020-04-09 14:30 payloadbob
0 siblings, 0 replies; only message in thread
From: payloadbob @ 2020-04-09 14:30 UTC (permalink / raw)
With debugging enabled you can log all kinds of stuff like malformed or replayed packets. However, debugging only tells you that something went wrong but it does not really show the cause.
It would be really nice if you could log those packets so you know exactly which packet caused an issue. Wireguard already knows about those. With external tools you would need to do lots of extra parsing and basically do everything twice. Also, I don't know to which extend tools like tcpdump/wireshark/iptables for logging traffic could handle all possible wireguard errors.
^ permalink raw reply [flat|nested] only message in thread
only message in thread, back to index
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-04-09 14:30 Log debug packets payloadbob
Development discussion of WireGuard
Archives are clonable: git clone --mirror http://inbox.vuxu.org/wireguard
Example config snippet for mirrors
Newsgroup available over NNTP:
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git