Skip to content

Instantly share code, notes, and snippets.

@tonusoo

tonusoo/bgp-vortex-lab.jpg

Last active October 23, 2025 15:34
Show Gist options

  • Select an option

    Learn more about clone URLs
  • Save tonusoo/1cced39aa6ae53143d12623a05f02331 to your computer and use it in GitHub Desktop.

Select an option

Learn more about clone URLs
Save tonusoo/1cced39aa6ae53143d12623a05f02331 to your computer and use it in GitHub Desktop.
Download ZIP
@tonusoo
Copy link
Author

tonusoo commented Oct 16, 2025 •
edited
Loading

Router "rZ" is running BIRD 3.1.4(single thread mode; all routes from BGP are synced to Linux kernel):
bgp-vortex-rZ-running-bird3

Router "rZ" is running FRR 10.4.1(niceness of bgpd and zebra has not been altered):
bgp-vortex-rZ-running-frr-default-niceness

All virtual machines are synced with the NTP server running on the host machine lab-svr.

@tonusoo
Copy link
Author

tonusoo commented Oct 23, 2025

rM had no out-delay configured:
rN-rL-UPDATE-messages_3600

rM had out-delay 1 under [edit protocols bgp]:
rN-rL-UPDATE-messages_with_out-delay_3600

BGP UPDATE messages were captured with tshark -w rN-rL-UPDATE-messages.pcap -i e-rN-rL -f 'src host 10.1.1.10 && dst host 10.1.1.11 && tcp && port 179' where e-rN-rL was a Linux bridge connecting the rN and rL virtual machines. The resulting rN-rL-UPDATE-messages.pcap file was then analyzed with a script that calculated the number of UPDATE messages per second and produced the data in a format suitable for gnuplot.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment