Hello! On 12/14/22 16:38, Nigel Kukard via Bird-users wrote:
Hi guys,
<pedantic> Sorry, I'm not a guy, yet I hope my answer helps you as well. </pedantic>
During testing of Bird 2.0.11 I noticed something a bit odd in terms of the output for RIP routes, is the below "RIP.02" and "<type 16>" expected?0001 BIRD 2.0.11 ready. 1007-Table t_kernel4: 192.168.21.0/24 unicast [rip4 2022-12-14 15:03:21] * (120/3) via 192.168.0.2 on eth0 1008- Type: RIP univ 1012- RIP.metric: 3 RIP.tag: 0000 RIP.02: *<type 16>* 1007-192.168.11.0/24 unicast [kernel4 2022-12-14 15:03:17] * (10) via 192.168.10.2 on eth1 1008- Type: inherit univ 1012- Kernel.source: 3 Kernel.metric: 0 0000
It's not expected to be written out, yet it's harmless otherwise. That attribute has always been there, just hidden. It looks like an incomplete backport of internal refactoring from v3 made it through to 2.0.11 and this attribute got unwantedly unhidden.
Sorry for the inconvenience. Please ignore that attribute for now. Maria
smime.p7s
Description: S/MIME Cryptographic Signature
