Network Analysis: Read a Bond's Mode from Captured Bonding Status

Analysis room: you read captured bonding status from another host and name one bond's mode. You don't create or configure a bond here.

Why: this lab box's kernel has no bonding driver, built in or loadable, so no bond can exist on it and it has no /proc/net/bonding/ of its own. Instead you analyse the kernel's view of bonds captured on a host that has them.

Three bonds carry that host's traffic, and one NIC keeps flapping. The kernel's view of every bond is captured under /root/net/bonding/ (copies of that host's /proc/net/bonding/bond0, bond1 and bond2), and `/root/net/task.txt` names the flapping NIC. The captures and the NIC are generated per session, so your answer differs from anyone else's.

Work out which bond that NIC is enslaved to, then record the bonding mode that bond runs, as the name you'd pass to the driver's mode= option: balance-rr, active-backup, balance-xor, broadcast, 802.3ad, balance-tlb or balance-alb (the numeric mode 0–6 is accepted too). The Bonding Mode: line uses the kernel's long description, so you have to map it.

Write it to /root/answers/bond_mode.txt.