RMCPPING(8)

📦
version 1.6.20 · 14 versions
, in arch rolling, centos-stream 10, centos-stream 9

💅 RMCPPING(8) — ok so this is rmcpping, from the System Commands girlies

Bestie. Sit down. We're doing RMCP Ping today and it's genuinely iconic.

🌸 NAME 🌸

rmcpping — send RMCP Ping to network hosts. That's it. That's the whole vibe.

✨ SYNOPSIS ✨

rmcpping [OPTION...] destination

🎀 DESCRIPTION 🎀

okay so here's the tea: rmcpping fires off an RMCP Ping request datagram at a remote host and waits for it to clap back with an RMCP Pong response. Rude? No. Iconic? Yes. It's literally how you verify if a remote host supports RMCP or IPMI — like a little vibe check for your BMC.

The initial starting sequence number is randomized, no cap. And here's the part you actually need to remember: rmcpping will return 0 to the environment if it receives at least 1 response from the remote host. Otherwise, it exits with a value of 1. Silence = 1. Ghosting is a fail, periodt. 💀

💖 OPTIONS 💖

The following options are available:

  • -h — Output help menu. Your lil safe space.
  • -V — Output version. Slay, what build are we on.
  • -c count — Stop after sending count packets. Boundaries! We love them!
  • -i interval — Wait interval seconds between sending each packet. The default is to wait for one second between each packet. Patience is a virtue etc etc.
  • -I interface address — Set source address to specified interface address. Argument may be numeric IP address or name of device. You can be flexible, I believe in you.
  • -t timeout — Time to wait for a response, in seconds. Default is five seconds. Five seconds of staring at your phone, basically.
  • -v — Verbose output. Give me every single detail, I want the whole story.
  • -s num — Specify an initial starting sequence number. The default is to use a random initial sequence number. (Yes, random is the default, we said that already, but consistency is cute.)
  • -d — Turn on debugging. For when it's giving bug and you need to know why.

😭 KNOWN ISSUES 😭

Okay this one's real. It has been observed that some remote BMCs can get "confused" and delay packet responses if duplicate packets (with duplicate sequence numbers) are sent in succession very quickly. Like, same energy repeated at them at 200mph. They just short-circuit. There is no known way to cleanly deal with a "confused" BMC other than to wait awhile. That's it. That's the fix. Go touch grass and come back. 🙈

Also, unlike ping(8), local network devices (e.g. 127.0.0.1) cannot be "pinged". Not a skill issue, it's just a thing. Note it, accept it, move on.

🫶 REPORTING BUGS 🫶

Report bugs to <freeipmi-users@gnu.org> or <freeipmi-devel@gnu.org>. They're nice, promise. Give them the receipts.

Copyright (C) 2007-2015 Lawrence Livermore National Security, LLC. Copyright (C) 2003-2007 The Regents of the University of California.

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 3 of the License, or (at your option) any later version.

Read the license, bestie. It's literally three lines and it's your whole legal situation. 💅

🌈 ORIGIN 🌈

Command and manpage based off ping(8). Yeah. It's a nepo baby. We still love it.

⭐ SEE ALSO ⭐

freeipmi(7), ping(8), ipmiping(8)

http://www.gnu.org/software/freeipmi/

🌸 ok that's the whole page, you ate that. this is rmcpping version 1.6.20, dated 2026-10-05, and it's a System Commands girlie through and through. go ping something (not 127.0.0.1, we been over this). mwah 💖🦋
📦 where this page comes from