bgpdump - translate MRT format files into readable output
Contents
Bugs
If a single update message contains more than 8192 added or withdrawn prefixes, all those above that
number are ignored.
Files with a name longer than 999 characters cannot be processed.
The bgpdump program is not y2038 compliant. This is inherited from the file format.
Debian
Besides bug fixes, the following changes were done in the packaging for the Debian distribution:
• The maximum number of prefixes processed from a single update
messages was raised from 2050 to 8192.
Input Formats
• MRT routing table dump entries in TABLE_DUMP or TABLE_DUMP_V2 types
• Zebra/Quagga BGP records:
• BGP messages (OPEN, UPDATE, NOTIFY, KEEPALIVE)
• BGP state changes
• File may be gzipped or bzip2'd and/or passed in through stdin
The file format is described in the Internet Draft grow-mrt-13: <https://tools.ietf.org/html/draft-ietf-
grow-mrt-13>
Name
bgpdump - translate MRT format files into readable output
Options
Output mode:
-H
multi-line, human-readable (the default)
-m
one-line per entry with unix timestamps
-M
one-line per entry with human readable timestamps in the form MM/DD/YY HH:MM:SS (there are other
differences between -m and -M)
Common options:
-O file
output to 'file' instead of STDOUT
-s
log to syslog (the default)
-v
log to STDERR
Options for -m and -M modes:
-tdump
timestamps for RIB dumps reflect the time of the dump (the default)
-tchange
timestamps for RIB dumps reflect the last route modification
-p
show packet index at second position
Special options:
-T
run internal tests and exit
Synopsis
Usage:
bgpdump [-m|-M] [-t dump|-t change] [-O <output-file>] <input-file>
Version
Version 1.4.99.15+hg127
