log the interface along with the neighbour ID in various ospfd/ospf6d
authorsthen <sthen@openbsd.org>
Wed, 3 Nov 2021 21:40:03 +0000 (21:40 +0000)
committersthen <sthen@openbsd.org>
Wed, 3 Nov 2021 21:40:03 +0000 (21:40 +0000)
commit9cc19ef17628f2b7f672f5d8fcfd93b184824033
tree859c6f628958728955e8a8c22e0f65a1dc9ccce3
parentdc2bea8abd37a88eea40374f0bec531ba41bebd9
log the interface along with the neighbour ID in various ospfd/ospf6d
messages.  ok remi@ benno@

if a neighbour is reachable over multiple network links, some problems
may be related to the link itself rather than the neighbour, so knowing
the interface can be important when trying to locate the source of a
problem.
12 files changed:
usr.sbin/ospf6d/database.c
usr.sbin/ospf6d/kroute.c
usr.sbin/ospf6d/lsack.c
usr.sbin/ospf6d/lsreq.c
usr.sbin/ospf6d/lsupdate.c
usr.sbin/ospf6d/neighbor.c
usr.sbin/ospfd/database.c
usr.sbin/ospfd/lsack.c
usr.sbin/ospfd/lsreq.c
usr.sbin/ospfd/lsupdate.c
usr.sbin/ospfd/neighbor.c
usr.sbin/ospfd/packet.c