# Wireguard debug log info?

**URL:** <https://forum.openwrt.org/t/wireguard-debug-log-info/90241>\
**Category:** Network and Wireless Configuration\
**Created:** [March 3, 2021, 8:27pm UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241 "2021-03-03T20:27:44Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![twinkleLED](https://forum.openwrt.org/user_avatar/forum.openwrt.org/twinkleled/32/9392_2.png) [@twinkleLED](https://forum.openwrt.org/u/twinkleLED)\
**Post date:** [March 3, 2021, 8:27pm UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241/1 "2021-03-03T20:27:44Z")

</div>

Wireguard on full Linux provides a nice way to get [Debug Info](https://www.wireguard.com/quickstart/#debug-info) out from the wg kernel module. It notes things like when wg initiates a handshake.

Is there something similar available when running Wireguard on OpenWrt?

---

<div class="post-metadata">

**Author:** ![vgaetera](https://forum.openwrt.org/user_avatar/forum.openwrt.org/vgaetera/32/113586_2.png) [@vgaetera](https://forum.openwrt.org/u/vgaetera)\
**Post date:** [March 3, 2021, 9:01pm UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241/2 "2021-03-03T21:01:40Z")

</div>

Build your own image with custom kernel config:

- [https://openwrt.org/docs/guide-developer/toolchain/start](https://openwrt.org/docs/guide-developer/toolchain/start)
- [https://github.com/openwrt/openwrt/blob/master/config/Config-kernel.in#L329-L339](https://github.com/openwrt/openwrt/blob/master/config/Config-kernel.in#L329-L339)

---

<div class="post-metadata">

**Author:** ![psherman](https://forum.openwrt.org/letter_avatar/psherman/32/5_5575768a8748004e209b776fc1b2916d.png) [@psherman](https://forum.openwrt.org/u/psherman)\
**Post date:** [March 4, 2021, 5:02am UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241/3 "2021-03-04T05:02:31Z")

</div>

Are you having specific issues currently? Or just interested in debug output in general?

---

<div class="post-metadata">

**Author:** ![twinkleLED](https://forum.openwrt.org/user_avatar/forum.openwrt.org/twinkleled/32/9392_2.png) [@twinkleLED](https://forum.openwrt.org/u/twinkleLED)\
**Post date:** [March 5, 2021, 6:31pm UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241/4 "2021-03-05T18:31:46Z")

</div>

No specific issues, but thanks for asking. It helps me understand the flow of wg control messages.

---

<div class="post-metadata">

**Author:** ![psherman](https://forum.openwrt.org/letter_avatar/psherman/32/5_5575768a8748004e209b776fc1b2916d.png) [@psherman](https://forum.openwrt.org/u/psherman)\
**Post date:** [March 5, 2021, 7:49pm UTC](https://forum.openwrt.org/t/wireguard-debug-log-info/90241/5 "2021-03-05T19:49:19Z")

</div>

Fair enough. The forum here has been able to help many users resolve WG issues without using the debug output, which is why I asked. I'm not sure how useful the debug output is for day-to-day activities, and it may slow things down a bit... but if you are curious, dig in... should be interesting to see what is in that output and hopefully it is useful for your situation!