BPING(1)

💖 BPING — the manual, but make it cute 💖

okay so this is bping from the BP executables section of the manual (that's the BPING(1) vibe if you're keeping score 🫶). sit down, grab a strawberry, we're gonna ping some bundles.

---

✨ NAME ✨

bping — send and receive Bundle Protocol echo bundles. literally that's it, that's the whole job. 💅

---

🎀 SYNOPSIS 🎀

bping [-c count] [-i interval] [-p priority] [-q wait] [-r flags] [-t
ttl] srcEID destEID [reporttoEID]

---

🌸 DESCRIPTION 🌸

so bping sends bundles from srcEID to destEID. that's the whole thing bestie. and if the destEID echoes those bundles back — like, for instance, if it's a bpecho endpoint 👀 — then bping will print the round-trip time for you. so cute.

when it's all done, bping prints statistics before it exits. very demure, very mindful. it's very similar to ping, except it works with the bundle protocol. same energy, different protocol, no cap.

now here's the part you gotta know: bping terminates when one of these happens —

1. it receives the SIGINT signal (that's your Ctrl+C, bestie, mwah 💅)
2. it receives responses to all of the bundles it sent
3. it has sent all count of its bundles and waited wait seconds

three ways out, pick your fighter. ✨

---

💀 EXIT STATUS 💀

these exit statuses are taken from ping. not invented, borrowed, iconic behavior.

• 0 — bping has terminated normally, and received responses to all the packets it sent. slay. 👑
• 1 — bping has terminated normally, but it did not receive responses to all the packets it sent. sad girl hours. 😭
• 2 — bping has terminated due to an error. details should be noted in the ion.log log file. go read the receipts. 🔥

---

🦋 FILES 🦋

No configuration files are needed. not one. zero. she's low maintenance. 💖

---

🌈 ENVIRONMENT 🌈

No environment variables apply. she doesn't care about your env, she's got her own vibe. ✨

---

💜 DIAGNOSTICS 💜

diagnostic messages produced by bping are written to the ION log file ion.log and printed to standard error. double the drama, double the info.

heads up bestie: diagnostic messages that don't cause bping to terminate mean there was a failure parsing an echo response bundle. which means destEID isn't an echo endpoint at all — it's responding with some other bundle message of an unexpected format. rude tbh. 🙈

here's the full roster of messages, translated:

• Can't attach to BP. — bpadmin has not yet initialized Bundle Protocol operations. go wake it up.
• Can't open own endpoint. — another application has already opened ownEndpointId. terminate that application and rerun. she's taken, sorry.
• bping bundle reception failed. — BP system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
• No space for ZCO extent. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
• Can't create ZCO. — ION system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.
• bping can't send echo bundle. — BP system error. check for earlier diagnostic messages describing the cause of the error; correct the problem and rerun.

---

🐛 BUGS 🐛

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — they're listening, fr fr. 🫶

---

👀 SEE ALSO 👀

bpecho(1), bptrace(1), bpadmin(1), bp(3), ping(8)

go read those too, iykyk. 💅

---

and that's the whole page babes — this version was living under perl v5.24.1, dated 2016-07-07, and it's still eating. periodt. 💖✨🎀