Incorrect nexthop when processing routeviews

Devin Bayer avatarDevin Bayer created an issue

Version: libbgpdump-

First reported to (RT#1005242)

We found a possible bug in the bgpdump cod when we processed some routeviews updates. Below is an example output for the same update with or without the -m option:

(without -m) TIME: 02/11/07 01:55:28 TYPE: BGP4MP/MESSAGE/Update FROM: AS2914 TO: AS6447 ORIGIN: INCOMPLETE ASPATH: 2914 10888 3948 16517 MULTI_EXIT_DISC: 348 MP_REACH_NLRI(IPv4 Multicast) NEXT_HOP: COMMUNITY: 2914:420 ANNOUNCE

(with -m) BGP4MP|1171158928|A||2914||2914 10888 3948 16517|INCOMPLETE||0|348|2914:420|NAG||

You can see that the nexthop field is incorrect when we use the -m option. I notice that the first output has MP_REACH_NLRI (IPv4 Multicast), so my guess is that the code for the -m option didn't retrieve the nexthop for the appropriate AFI/SAFI option.

Comments (0)

  1. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.