GNUNET-TRANSPORT(1)

💖 GNUNET-TRANSPORT(1) 💖

okay bestie, sit down, hydrate, and let me tell you about gnunet-transport — a General Commands Manual girlie whose whole job is measuring and controlling the transport subsystem. she's from the GNUnet fam and she is, frankly, iconic. 🦋

✨ NAME ✨

gnunet-transport — measure and control the transport subsystem, periodt. 💅

🌸 SYNOPSIS 🌸

gnunet-transport [-b | --benchmark] [-c FILENAME | --config=FILENAME]
                 [-D | --disconnect] [-e | --events] [-h | --help]
                 [-i | --information]
                 [-L LOGLEVEL | --loglevel=LOGLEVEL]
                 [-l LOGFILE | --logfile=LOGFILE] [-m | --monitor]
                 [-p PEER | --peer=PEER] [-P | --plugins] [-s | --send]
                 [-v | --version] [-V | --verbose]

💜 DESCRIPTION 💜

so, gnunet-transport is literally a tool that lets you poke at all kinds of functions inside GNUnet's transport subsystem straight from the command line. no GUI, no drama, just you and your terminal having a moment. ✨

ngl though, most of these functions are not expected to be useful for end-users — like, this is not the brunch-menu-friendly part of GNUnet, it's giving dev-tools energy. 🙈

what can she do? she can be used to evaluate the performance of the transports, and to force a peer to connect to another peer (if possible). the "if possible" is doing a lot of heavy lifting there, bestie — read it as written, no cap. and the manpage says other functions should be added in the near future, so consider this a glow-up in progress. 💅

🎀 the options, one by one, no skips 🎀

• -b, --benchmark — Measure how fast we are receiving data (from all connections). On exit, the data rate will be reported. Runs until aborted with CTRL-C. so like, it just goes, and you hit CTRL-C when you've seen enough. 💀
• -c FILENAME, --config=FILENAME — configuration file to use. the file you point at, that's the one she'll use.
• -D, --disconnect — Force disconnection from a peer (used in conjunction with -p). Note that you can use the gnunet-ats command-line tool to suggest connects. 🫶 so -D is the "we're done here" button, and gnunet-ats is the "hey maybe try connecting" suggester.
• -e, --events — Provide information about all connect and disconnect events (continuously). continuously! it does not stop. it's committed.
• -h, --help — Print the help page. classic, beloved.
• -i, --information — Print information about our current connections (once). once only, bestie. one and done.
• -L LOGLEVEL, --loglevel=LOGLEVEL — Change the loglevel. Possible values for LOGLEVEL are ERROR, WARNING, INFO and DEBUG. ✨
• -l LOGFILE, --logfile=LOGFILE — Configure logging to write logs to LOGFILE.
• -m, --monitor — Print information about our current connections (continuously). yeah she's the -i girlie but she never stops. main character energy. 👑
• -p PEER, --peer=PEER — The peer identity to connect to or monitor. this is your target, your person, your peer. 💖
• -P, --plugins — Monitor session state of transport plugins.
• -s, --send — Transmit (dummy) traffic as quickly as possible to the peer specified with the -p option. The rate will still be limited by the quota(s) determined by the peers (ATS subsystem). Will run until CTRL-C is pressed or until the connection to the other peer is disrupted. so yeah — "as quickly as possible" but also ATS said no and set a quota. it runs until you CTRL-C or the connection dies. 😭
• -v, --version — Print out the version number.
• -V, --verbose — be verbose. that's it, that's the whole description. she's chatty, let her be. 🦋

🌈 SEE ALSO 🌈

• gnunet-arm(1), gnunet-ats(1)

also, the full documentation for gnunet is maintained as a Texinfo manual. if the info(1) and gnunet programs are properly installed at your site, the command

info gnunet

should give you access to the complete handbook,

info gnunet-c-tutorial

will give you access to a tutorial for developers.

depending on your installation, this information is also available in gnunet(7) and gnunet-c-tutorial(7). 💜

⭐ BUGS ⭐

found something cursed? Report bugs by using https://bugs.gnunet.org or by sending electronic mail to ⟨gnunet-developers@gnu.org⟩. please be nice, they're trying their best. 🫶

and that's the whole page, bestie!! this one shipped from Debian, dated October 17, 2015, and it's the GNUNET-TRANSPORT(1) page in all its glory. go forth and benchmark something. slay. 💅✨🎀