STCPCLO(1)

📦 version 3.2.1, in ubuntu jammy

💅 STCPCLO — the it-girl of TCP outducts 💅

okay bestie, gather round, because we're talking about stcpclo(1) — a BP executable and honestly? she's giving backstage main character energy. This is the DTN simple TCP convergence layer adapter output task. Say that five times fast. Or don't. I didn't.

✨ SYNOPSIS ✨

stcpclo remote_hostname[:remote_port_nbr]

🦋 DESCRIPTION 🦋

So stcpclo is a background "daemon" task, and the way she works is: she connects to a remote node's TCP socket at remote_hostname and remote_port_nbr. Then she starts pulling bundles out of the queues of bundles that are ready to be transmitted over TCP to this remote bundle protocol agent, and she sends those bundles across the connected socket to that node. Literally just vibes and bundles.

Every single transmitted bundle gets a lil glow-up first: it's preceded by a 32-bit integer in network byte order indicating the length of the bundle. That's her signature move. 💖

If you don't specify it, remote_port_nbr defaults to 4556. Periodt.

🫶 important boundary moment: stcpclo is not a "promiscuous" convergence layer daemon. She can transmit bundles only to the node she's connected to. So scheme configuration directives that cite this outduct only need to provide the protocol name and the outduct name as specified on the command line when stcpclo was started. She's loyal, ok?!

stcpclo gets spawned automatically by bpadmin in response to the 's' (START) command that starts operation of the Bundle Protocol, and she gets terminated by bpadmin in response to an 'x' (STOP) command. She can also be spawned and terminated in response to START and STOP commands that pertain specifically to the STCP convergence layer protocol. So she can show up for the big group thing or just for the STCP-specific party. versatile icon behavior ✨

🔥 EXIT STATUS 🔥

  • "0" — stcpclo terminated normally, for reasons noted in the ion.log file. If this termination was not commanded, investigate and solve the problem identified in the log file and use bpadmin to restart the STCP protocol.
  • "1" — stcpclo 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 the STCP protocol.

ngl both of these end with "go read ion.log and then restart with bpadmin" and honestly that's the whole personality.

🎀 FILES 🎀

No configuration files are needed. She came with everything she needs. lowkey refreshing 💅

🌸 ENVIRONMENT 🌸

No environment variables apply. She does not need your shell to set the mood. she IS the mood.

💀 DIAGNOSTICS 💀

These are the diagnostics that may be issued to the ion.log log file. Read them, they're not subtle:

  • stcpclo can't attach to BP. — bpadmin has not yet initialized Bundle Protocol operations. like girl. you gotta start the thing first.
  • No such stcp duct. — No STCP outduct with duct name matching remote_hostname and remote_port_nbr has been added to the BP database. Use bpadmin to stop the STCP convergence-layer protocol, add the outduct, and then restart the STCP protocol. three-step skincare routine, do it in order.
  • CLO task is already started for this duct. — Redundant initiation of stcpclo. she's already here bestie, stop summoning her 😭
  • Can't get IP address for host — Operating system error. Check errtext, correct problem, and restart STCP.

🙈 BUGS 🙈

Report bugs to <ion-bugs@korgano.eecs.ohiou.edu> — they're genuinely nice and they will fix it fr fr. Don't be shy, tell them everything.

🌈 SEE ALSO 🌈

bpadmin(1), bprc(5), stcpcli(1) — the whole friend group, go say hi.

and that's the page!! this was written by perl v5.24.1 on 2016-07-07, so if you're reading this years later just know she's an elder icon and she's still slaying 💖✨🎀 bye bestie, go transmit some bundles 🦋

📦 where this page comes from