Ondrej Zajicek 6d1ae197d1 Nest: Fix several issues with pflags ... There were some confusion about validity and usage of pflags, which caused incorrect usage after some flags from (now removed) protocol- specific area were moved to pflags. We state that pflags: - Are secondary data used by protocol-specific hooks - Can be changed on an existing route (in contrast to copy-on-write for primary data) - Are irrelevant for propagation (not propagated when changed) - Are specific to a routing table (not propagated by pipe) The patch did these fixes: - Do not compare pflags in rte_same(), as they may keep cached values like BGP_REF_STALE, causing spurious propagation. - Initialize pflags to zero in rte_get_temp(), avoid initialization in protocol code, fixing at least two forgotten initializations (krt and one case in babel). - Improve documentation about pflags		2023-01-01 20:10:23 +01:00
..
config.Y	Nest: Per-channel debug flags	2020-12-07 22:19:40 +01:00
Doc	Doc: Rename code documentation files back to Doc	2018-12-14 02:03:42 +01:00
Makefile	Simplified the protocol hookup code in Makefiles	2022-08-18 22:07:30 +02:00
pipe.c	Nest: Fix several issues with pflags	2023-01-01 20:10:23 +01:00
pipe.h	Channels - explicit links between protocols and tables	2016-02-01 10:28:50 +01:00