sraustein
commented
13 years ago Sure looks like a router bug. 3.0.0.0 appears exactly once in the output of a session using rtr-origin --client. Furthermore, the immediate error report from the router in question is somewhat suspicious, given that the table is large enough that I would expect it to take at least a few seconds to transfer.
Trac comment by sra on 2011-09-07T14:21:46Z
{{{ Sep 7 13:52:04 dfw0 rtr-origin/bgpdump_server/tcp/147.28.0.9:63230[62164]: [serial_query, serial #1293235217 nonce 0] Sep 7 13:52:04 dfw0 rtr-origin/bgpdump_server/tcp/147.28.0.9:63230[62164]: [Client requested wrong nonce, resetting client] Sep 7 13:52:04 dfw0 rtr-origin/bgpdump_server/tcp/147.28.0.9:63230[62164]: [reset_query] Sep 7 13:52:04 dfw0 rtr-origin/bgpdump_server/tcp/147.28.0.9:63230[62164]: [error_report, error #7: 'Duplicate announce for prefix 3.0.0.0/8 ASN 80'] Sep 7 13:52:04 dfw0 rtr-origin/bgpdump_server/tcp/147.28.0.9:63230[62164]: [Shutting down due to reported fatal protocol error] }}}
I'm suspicous of this report, as it's just this one client that claims we're sending a duplicate, but let's check.
_Trac ticket #73 component rtrorigin priority minor, owner sra, created by sra on 2011-09-07T13:54:13Z, last modified 2011-09-07T14:21:46Z