DCCPCLI(1)

💖 DCCPCLI — the glow-up edition ✨

okay so this is dccpcli(1) from the BP executables fam, and she's a whole vibe. let's get into it 🫶

---

✨ NAME ✨

dccpcli — a DCCP-based BP convergence layer input task, aka the girl who sits there listening for datagrams so you don't have to 💅

---

🌸 SYNOPSIS 🌸

dccpcli local_hostname[:local_port_nbr]

---

🦋 DESCRIPTION 🦋

so dccpcli is a background "daemon" task — yes bestie, the quotes are in the original, she's a daemon daemon 💀 — and what she does is: she receives DCCP datagrams over a DCCP socket bound to local_hostname and local_port_nbr, she pulls the bundles out of those datagrams, and she hands them straight to the bundle protocol agent on the local ION node. no cap, that's the whole job. 👑

if you don't specify a port number, it just defaults to 4556. cute. 🎀

lowkey important: dccpcli has no fragmentation support at all. like, zero. none. so the biggest bundle you can send over this convergence layer is capped at just under the link's MTU — typically 1500 bytes. plan accordingly bestie 😭

the convergence layer input task gets spawned automatically by bpadmin in response to the s (START) command that starts operation of the Bundle Protocol. the text of the command used to spawn the task has to be provided at the time the dccp convergence layer protocol is added to the BP database. and the convergence layer input task gets terminated by bpadmin in response to an x (STOP) command. dccpcli can also be spawned and terminated in response to START and STOP commands that pertain specifically to the DCCP convergence layer protocol. so like, two ways in, two ways out. iconic. ✨

---

⭐ EXIT STATUS ⭐

• "0" — dccpcli terminated normally, for reasons noted in the ion.log file. if this termination was not commanded, go investigate and solve the problem identified in the log file, then use bpadmin to restart dccpcli. 🫶
• "1" — dccpcli terminated abnormally, for reasons noted in the ion.log file. investigate and solve the problem identified in the log file, then use bpadmin to restart dccpcli. 😭

---

🎀 FILES 🎀

no configuration files are needed. not a single one. she's low maintenance fr fr 💖

---

🌈 ENVIRONMENT 🌈

no environment variables apply. nope. none. the environment stays out of her business 💅

---

🔥 DIAGNOSTICS 🔥

these are the diagnostics that may get issued to the ion.log log file. buckle up bestie:

• dccpcli can't attach to BP. — bpadmin has not yet initialized Bundle Protocol operations.
• No such dccp duct. — no DCCP induct matching local_hostname and local_port_nbr has been added to the BP database. use bpadmin to stop the DCCP convergence-layer protocol, add the induct, and then restart the DCCP protocol.
• CLI task is already started for this duct. — redundant initiation of dccpcli.
• dccpcli can't get IP address for host. — operating system error. check errtext, correct the problem, and restart dccpcli.
• CLI can't open DCCP socket. This probably means DCCP is not supported on your system. — operating system error. this probably means you're not using an operating system that supports DCCP. make sure you're using a current Linux kernel and that the DCCP modules are being compiled. check errtext, correct the problem, and restart dccpcli. 💀
• CLI can't initialize socket. — operating system error. check errtext, correct the problem, and restart dccpcli.
• dccpcli can't get acquisition work area. — ION system error. check errtext, correct the problem, and restart dccpcli.
• dccpcli can't create new thread. — operating system error. check errtext, correct the problem, and restart dccpcli.

---

💀 BUGS 💀

report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — yes, that's the email, put it in your contacts bestie 🙈

---

👑 SEE ALSO 👑

bpadmin(1), bprc(5), dccpclo(1) — go read those too, they're part of the same friend group 🦋

---

and that's the whole page!! this one came from BP executables, documented as of 2016-07-07, and the page itself was generated by perl v5.24.1. slay, drink water, and go check your ion.log 💖✨🧚