[SECNET PATCH 00/14] Better logging of NAK reasons
Ian Jackson
ijackson at chiark.greenend.org.uk
Sat Sep 21 17:07:45 BST 2019
chiark seems to be sending NAKs for a peer for which we don't have
local configuration. At least, that's what I think is happening.
Improve secnet's logging for these kind of cases.
Ian Jackson (14):
buffer: Abolish unused `flags'
util: truncmsg: New way of manipulating buffers
util: priomsg: New facility
util: priomsg: Allow passing priomsg_update_p a null pm
comm: comm_notify takes the cc, not just the notify_list
comm: Introduce commcommon->why_unwanted
util: Reorder information in NAK log messages
udp: Use commcommon->why_unwanted
site: Pass whynot through to named_for_us
site: named_for_us: Introduce NAME_MATCHES
site: named_for_us: Reorganise into "if"s
site: Record whynot in default (end of comm_notify) case
util: priomsg: Provide and use priomsg_update_fixed
site: Provide NAK reasons mentioning names and unpick failure
comm-common.c | 8 ++++--
comm-common.h | 8 +++---
secnet.h | 14 +++++++++--
site.c | 35 ++++++++++++++++++++------
udp.c | 6 +++--
util.c | 81 +++++++++++++++++++++++++++++++++++++++++++++++++++++++----
util.h | 35 ++++++++++++++++++++++++++
7 files changed, 165 insertions(+), 22 deletions(-)
--
2.11.0
More information about the sgo-software-discuss
mailing list