From 25c3babb4be39241bf3c463cd283f1996beb41b2 Mon Sep 17 00:00:00 2001
From: Bryan Biedenkapp <gatekeep@gmail.com>
Date: Wed, 30 Oct 2024 14:57:20 -0400
Subject: [PATCH] when a NAK is directly written to a end-point address log the
 address;

---
 src/fne/network/FNENetwork.cpp | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/src/fne/network/FNENetwork.cpp b/src/fne/network/FNENetwork.cpp
index 8c2ff3ca..d357ad3b 100644
--- a/src/fne/network/FNENetwork.cpp
+++ b/src/fne/network/FNENetwork.cpp
@@ -10,6 +10,7 @@
 #include "fne/Defines.h"
 #include "common/edac/SHA256.h"
 #include "common/network/json/json.h"
+#include "common/network/tcp/Socket.h"
 #include "common/zlib/zlib.h"
 #include "common/Log.h"
 #include "common/Utils.h"
@@ -2396,6 +2397,7 @@ bool FNENetwork::writePeerNAK(uint32_t peerId, const char* tag, NET_CONN_NAK_REA
     __SET_UINT16B((uint16_t)reason, buffer, 10U);                               // Reason
 
     logPeerNAKReason(peerId, tag, reason);
+    LogWarning(LOG_NET, "PEER %u NAK %s, %s:%u", peerId, tag, (uint16_t)reason, tcp::Socket::address(addr).c_str(), tcp::Socket::port(addr));
     return m_frameQueue->write(buffer, 12U, createStreamId(), peerId, m_peerId,
         { NET_FUNC::NAK, NET_SUBFUNC::NOP }, 0U, addr, addrLen);
 }