Hi, while debugging some bridge configuration issue I wasnt able to get a complete picture of the bridge configuration handling inside netifd out of the box, so I would like to propose following two relatively small changes which helped me better understand netifd internals by using just a debugging output and ubus.
First patch is going to output bitset of changed device/bridge settings in debugging output, so one can find out why the bridge was reloaded. Second patch adds currently missing bridge attributes into the ubus bridge device status dump. Cheers, Petr Cc: Felix Fietkau <[email protected]> Petr Štetiar (2): bridge: make it more clear why the config was applied bridge: bridge_dump_info: add dumping of bridge attributes bridge.c | 40 ++++++++++++++++++++++++++++++++++++---- 1 file changed, 36 insertions(+), 4 deletions(-) _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
