1
0

bgpdump.txt 2.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121
  1. BGPDUMP(1)
  2. ==========
  3. NAME
  4. ----
  5. bgpdump - translate MRT format files into readable output
  6. VERSION
  7. -------
  8. Version 1.4.99.15+hg127
  9. SYNOPSIS
  10. --------
  11. Usage:
  12. ----
  13. bgpdump [-m|-M] [-t dump|-t change] [-O <output-file>] <input-file>
  14. ----
  15. OPTIONS
  16. -------
  17. Output mode:
  18. *-H*::
  19. multi-line, human-readable (the default)
  20. *-m*::
  21. one-line per entry with unix timestamps
  22. *-M*::
  23. one-line per entry with human readable timestamps in the form
  24. MM/DD/YY HH:MM:SS (there are other differences between -m and -M)
  25. Common options:
  26. *-O 'file'*::
  27. output to 'file' instead of STDOUT
  28. *-s*::
  29. log to syslog (the default)
  30. *-v*::
  31. log to STDERR
  32. Options for -m and -M modes:
  33. *-t dump*::
  34. timestamps for RIB dumps reflect the time of the dump (the default)
  35. *-t change*::
  36. timestamps for RIB dumps reflect the last route modification
  37. *-p*::
  38. show packet index at second position
  39. Special options:
  40. *-T*::
  41. run internal tests and exit
  42. INPUT FORMATS
  43. -------------
  44. * MRT routing table dump entries in TABLE_DUMP or TABLE_DUMP_V2 types
  45. * Zebra/Quagga BGP records:
  46. ** BGP messages (OPEN, UPDATE, NOTIFY, KEEPALIVE)
  47. ** BGP state changes
  48. * File may be gzipped or bzip2'd and/or passed in through stdin
  49. The file format is described in the Internet Draft grow-mrt-13:
  50. <https://tools.ietf.org/html/draft-ietf-grow-mrt-13>
  51. BUGS
  52. ----
  53. If a single update message contains more than 8192 added or
  54. withdrawn prefixes, all those above that number are ignored.
  55. Files with a name longer than 999 characters cannot be processed.
  56. The bgpdump program is not y2038 compliant. This is inherited from
  57. the file format.
  58. DEBIAN
  59. ------
  60. Besides bug fixes, the following changes were done in the packaging
  61. for the Debian distribution:
  62. * The maximum number of prefixes processed from a single update
  63. messages was raised from 2050 to 8192.
  64. AUTHOR
  65. ------
  66. bgpdump was originally written by Dan Ardelean and the RIPE NCC
  67. took over maintenance in 2005.
  68. bgpdump is Copyright (C) 2007-2011 RIPE NCC
  69. This manpage is based on bgpdump's usage output, the bgpdump's
  70. homepage, and other sources. It was written for the Debian project
  71. by Christoph Biedl <debian.axhn@manchmal.in-ulm.de> but may be used
  72. by others.