BGPDUMP(1)

πŸ“¦
version 1.6.2 Β· 3 versions
, in debian bookworm, ubuntu jammy, ubuntu noble

πŸ’– BGPDUMP β€” okay bestie, let's talk about bgpdump πŸ’–

bgpdump(1) β€” the manual page you're literally reading right now. Pull up a chair, grab a boba, we're decoding MRT files together. πŸ§‹βœ¨


🌸 NAME 🌸

bgpdump β€” translates MRT format files into readable output. That's the whole vibe. It takes those cursed binary blobs and makes them legible. πŸ’…


πŸŽ€ VERSION πŸŽ€

Version 1.4.99.15+hg127 β€” yes, that's the whole number, no cap. πŸ‘‘


✨ SYNOPSIS ✨

Usage, babes:

bgpdump [-m|-M] [-t dump|-t change] [-O <output-file>] <input-file>

That's it. That's the incantation. πŸͺ„


πŸ”₯ OPTIONS πŸ”₯

πŸ’« Output mode πŸ’«

Pick your fighter, bestie:

  • -H β€” multi-line, human-readable. This is the default, so if you don't say anything, this is what you get. 🫢
  • -m β€” one line per entry, with unix timestamps. Compact queen energy.
  • -M β€” one line per entry, with human readable timestamps shaped like MM/DD/YY HH:MM:SS. And listen β€” there are other differences between -m and -M, so don't assume they're twins. They are not. 😭

🌈 Common options 🌈

  • -O file β€” output goes to file instead of STDOUT. Redirect your whole life. πŸ’–
  • -s β€” log to syslog. This is the default, iconic behaviour honestly.
  • -v β€” log to STDERR instead. For when you want the tea right there in your terminal. πŸ“

πŸ¦‹ Options for -m and -M modes πŸ¦‹

These only hit different when you're in -m or -M land, iykyk:

  • -t dump β€” timestamps for RIB dumps reflect the time of the dump. This is the default.
  • -t change β€” timestamps for RIB dumps reflect the last route modification instead.
  • -p β€” show the packet index at the second position. Number two. Right there. πŸ“

πŸ‘‘ Special options πŸ‘‘

  • -T β€” run internal tests and then exit. It's giving "I'm just here to check myself, bye". 🧚

🌟 INPUT FORMATS 🌟

What can you feed this thing? Bestie, let me list it out:

  • 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. Yes, you can pipe it. Live your truth. 🫢

The file format is described in the Internet Draft grow-mrt-13:

https://tools.ietf.org/html/draft-ietf-grow-mrt-13

Go read it if you want the deep lore. πŸ“š


πŸ’€ BUGS πŸ’€

Okay so, not everything is perfect, and we're being honest about it:

  • If a single update message contains more than 8192 added or withdrawn prefixes, all those above that number are ignored. Gone. Poof. 🫠
  • Files with a name longer than 999 characters cannot be processed. 999 is the limit, 1000 is a crime scene.
  • The bgpdump program is not y2038 compliant. This is inherited from the file format, so it's not even bgpdump's fault, it's generational trauma. 😭

πŸ“ 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. Debian said "actually, let's raise the ceiling" and honestly? Slay. πŸ’…

πŸ’œ AUTHOR πŸ’œ

bgpdump was originally written by Dan Ardelean and the RIPE NCC took over maintenance in 2005. Shoutout to the maintainers fr fr. 🫢

bgpdump is Copyright Β© 2007-2011 RIPE NCC.

This manpage is based on bgpdump's usage output, the bgpdump's homepage, and other sources. It was written for the Debian project by Christoph Biedl <debian.axhn@manchmal.in-ulm.de> but may be used by others. Generous king behaviour. πŸ‘‘


And that's the whole page, bestie. You made it to the end of BGPDUMP(1) β€” version 1.4.99.15+hg127, Debian packaging and all. Periodt. πŸ’–βœ¨πŸŽ€
πŸ“¦ where this page comes from