This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
Multicast pkts in bgpdump being mixed with unicast pkts?
- Previous message (by thread): Do we like the same books?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Ricardo V. Oliveira
rveloso at cs.ucla.edu
Sat Nov 10 15:50:39 CET 2007
Hi, For some reason, bgpdump is now reporting multicast entries mixed w/ unicast. In the example bellow taken from http://archive.routeviews.org/route-views.linx/bgpdata/2007.10/ UPDATES/updates.20071031.1156.bz2 There are these 8 multicast announcements that get mixed with the unicast ones when you do "bgpdump -m": TIME: 10/31/07 12:09:15 TYPE: BGP4MP/MESSAGE/Update FROM: 195.66.224.138 AS2914 TO: 195.66.225.222 AS6447 ORIGIN: IGP ASPATH: 2914 24 226 567 2152 2153 11537 5511 MULTI_EXIT_DISC: 342 MP_REACH_NLRI(IPv4 Multicast) NEXT_HOP: 195.66.224.138 COMMUNITY: 2914:420 2914:2000 2914:3000 65504:24 ANNOUNCE 202.87.97.0/24 TIME: 10/31/07 12:09:17 TYPE: BGP4MP/MESSAGE/Update FROM: 195.66.224.138 AS2914 TO: 195.66.225.222 AS6447 ORIGIN: IGP ASPATH: 2914 24 226 567 2152 2153 11537 5511 MULTI_EXIT_DISC: 342 MP_REACH_NLRI(IPv4 Multicast) NEXT_HOP: 195.66.224.138 COMMUNITY: 2914:420 2914:2000 2914:3000 65504:24 ANNOUNCE 202.87.80.0/24 202.87.86.0/23 202.87.117.0/24 202.87.98.0/23 202.87.102.0/24 202.87.101.0/24 202.87.81.0/24 BGP4MP|1193832555|A|195.66.224.138|2914|202.87.97.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.80.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.86.0/23|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.117.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.98.0/23|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.102.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.101.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| BGP4MP|1193832557|A|195.66.224.138|2914|202.87.81.0/24|2914 24 226 567 2152 2153 11537 5511|IGP|255.255.255.255|0|342|2914:420 2914:2000 2914:3000 65504:24|NAG|| Is there any plan to fix this or at least add a field with the AFI to the records? Thanks, --Ricardo
- Previous message (by thread): Do we like the same books?
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]