Original issue: CAIDA/libbgpstream#159

bgpreader -d singlefile -o rib-file=https://www.isolario.it/Isolario_MRT_data/Alderaan/2019_12/rib.20191211.0800.bz2 1>/dev/null
WARN: No time window specified, defaulting to all available data
2019-12-11 08:03:49 51094: bgpstream_parsebgp_common.c:594: ERROR: Failed to parse message from 'https://www.isolario.it/Isolario_MRT_data/Alderaan/2019_12/rib.20191211.0800.bz2' (-2:Invalid Message)

• libbgpstream version: CAIDA/libbgpstream@64daa62.
• libparsebgp version: ce34041

Hi, I got the same issue when I parsing the isolario rib data, I just wondered whether the issue has been solved.

Hello, I have reinstalled the bgpstream, but it got the same issue when I use it to parse the isolario's MRT data in 2020.

bgpreader -d singlefile -o rib-file=rib.20201101.0000 -m > temp
WARN: No time window specified, defaulting to all available data
2020-12-02 16:43:22 18962: bgpstream_parsebgp_common.c:601: ERROR: Failed to parse message from 'rib.20201101.0000' (-2:Invalid Message)

@x-bin could you provide a download link to the file you're having trouble parsing?

@kenkeys could you take a look at the error occurred with the following command?
bgpreader -d singlefile -o rib-file=https://www.isolario.it/Isolario_MRT_data/Alderaan/2019_12/rib.20191211.0800.bz2
It prints out a bunch of records, but terminates very early with the error message
2020-12-02 05:39:45 1116054: bgpstream_parsebgp_common.c:599: ERROR: Failed to parse message from 'https://www.isolario.it/Isolario_MRT_data/Alderaan/2019_12/rib.20191211.0800.bz2' (-2:Invalid Message)

The message that triggers the error has TABLE_DUMP_V2 subtype 8, which isn't implemented in libparsebgp. It was defined by RFC 8050 in 2017 to allow a message to contain additional paths. Implementing that will take some work.

@x-bin could you provide a download link to the file you're having trouble parsing?

Sure, the link is https://isolario.it/Isolario_MRT_data/Alderaan/2020_11/rib.20201101.0000.bz2

The message that triggers the error has TABLE_DUMP_V2 subtype 8, which isn't implemented in libparsebgp. It was defined by RFC 8050 in 2017 to allow a message to contain additional paths. Implementing that will take some work.

@kenkeys Do you think we could change the behaviour to throw unimplemented warning instead of error out?