Maria Matejka 17f91f9e6e Explicit definition structures of route attributes ... Changes in internal API: * Every route attribute must be defined as struct ea_class somewhere. * Registration of route attributes known at startup must be done by ea_register_init() from protocol build functions. * Every attribute has now its symbol registered in a global symbol table defined as SYM_ATTRIBUTE * All attribute ID's are dynamically allocated. * Attribute value custom formatting hook is defined in the ea_class. * Attribute names are the same for display and filters, always prefixed by protocol name. Also added some unit testing code for filters with route attributes.		2022-05-04 15:39:19 +02:00
..
config.Y	Explicit definition structures of route attributes	2022-05-04 15:39:19 +02:00
Doc	Doc: Rename code documentation files back to Doc	2018-12-14 02:03:42 +01:00
Makefile	Protocols have their own explicit init routines	2022-04-06 18:14:08 +02:00
packets.c	Configuration strings are constant.	2020-04-09 15:37:14 +02:00
radv.c	Explicit definition structures of route attributes	2022-05-04 15:39:19 +02:00
radv.h	Explicit definition structures of route attributes	2022-05-04 15:39:19 +02:00