Warnings when using IPv6-Adresses for BMP-communication / Release request

[NkPlugge]

We use IPv6-Adresses in the config.yaml for BMP-communication like this: api: bind: "[::1]:3000" collectors:

• collector_type: Bmp bind: "[::]:11020" peers: "2a02:X:X:X::X": {} "2a02:X:X:X::X": {}

When starting the fernglas.service, the following warnings occur:

fernglas[9332]: [2023-11-29T21:52:34Z WARN fernglas::bmp_collector] BMP Parse Error: Static("Invalid addrv4 length") fernglas[9332]: [2023-11-29T21:52:34Z WARN fernglas::bmp_collector] b"\x03\0\0\x019\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\xb9\x8f\xa9\xe1\0\0\xa4\xc8\n\x06\0\x0ceT\x1c\xb3\0\x05\xfb\xc0\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\x01\t\x02\0\0\0\xf2@\x01>... fernglas[9332]: [2023-11-29T21:52:34Z WARN fernglas::bmp_collector] BMP Parse Error: Static("Invalid addrv4 length") fernglas[9332]: [2023-11-29T21:52:34Z WARN fernglas::bmp_collector] b"\x03\0\0\x019\0\0@\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\xb9\x8f\xa9\xe1\0\0\xa4\xc8\n\x06\0\x0ceT\x1c\xb3\0\x05\xfb\xc0\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\xff\x01\t\x02\0\0\0\xf2@\x01>...

Is there a way, that we are using IPv6 addresses wrong in the config-file? Or is there maybe already a fix for something like this in the current repo? We also see huge differences in https://lg.as9136.net/#/ and the front- and backend you get when using release 0.1.0 of this repo? Maybe you can do us the favor and create a new release with from the current code?

[yu-re-ka]

The warnings are originated from the zettabgp library. This can happen if zettabgp has not implemented certain types of address families (maybe EVPN?). We also see these kinds of warnings in our instances, it should not impact normal operation of fernglas, but if you want to get rid of the warnings you can attempt to limit what BGP sessions are distributed via BMP by configuring this on your router.

If you use IPv4 or IPv6 for the BMP transport should not matter at all. The content of the BMP stream is the same.

We are going to make a release once some currently work-in-progress changes are done. Until then, you can use the current master, and let us know if you have any issues.