ipmilan(8)

✨ ipmilan — the IPMI LAN to System Interface Converter ✨

okay bestie, gather round, because ipmilan is that girl 💅 — it's the ipmilan(8) manual page, and it's lowkey one of the most useful daemons in the OpenIPMI universe. Let's get into it 🫶

---

🌸 NAME 🌸

ipmilan — IPMI LAN to System Interface Converter ✨

---

🎀 SYNOPSIS 🎀

ipmilan [-c configfile] [-i ipmidevice] [-d] [-n]

---

💖 DESCRIPTION 💖

So basically, the ipmilan daemon lets an IPMI system interface that's using the OpenIPMI device driver be accessed through the IPMI 1.5 or 2.0 LAN protocol. That's the whole vibe ✨

ipmilan supports the full authentication capabilities of the IPMI LAN protocol — like, all of them, no cap 🔥

It also supports multiple IP addresses for fault-tolerance, because resilience is main character energy 👑 Just know that messages coming in on an address are always sent back out on the same address they came in on. No switcheroos, periodt.

---

🌈 OPTIONS 🌈

• -c config-file — sets the configuration file to something other than the default of /etc/ipmi_lan.conf. Iconic. Pick your own path bestie 💖
• -n — stops the daemon from forking and detaching from the controlling terminal. This is useful for running from init. no detaching, no disappearing, we stay 👀
• -d — turns on debugging to standard output. You generally have to use -n with this one. Like, they're a package deal fr fr 🎀

---

💜 CONFIGURATION 💜

All the configuring happens through the file /etc/ipmi_lan.conf 🗂️ If you want a file with another name or path, just hit it with the -c option. For more details, go read the ipmi_lan config file man page — it's got the tea ☕

---

🔥 SECURITY 🔥

ipmilan implements normal IPMI security. The default is no access for anyone, so like, the default is pretty safe 🛡️ But be careful what you add, because this is literally access to control your box. That's not a small thing bestie 😭

straight and none authorizations are not recommended. You should probably stick with md2 or md5. This is a hard vibe check and you should pass it 💅

---

⭐ SIGNALS ⭐

SIGHUP

ipmilan should handle SIGHUP and reread its configuration files. However... it doesn't right now 🙈 It might in the future, but for now you will have to kill it and restart it. Clients should handle reconnecting in this case. If they don't, they are broken 💀

---

🦋 ERROR OUTPUT 🦋

At startup, all error output goes to stderr. After that, all error output goes to syslog. Two phases, two destinations, that's just how she rolls ✨

---

🍓 FILES 🍓

/etc/ipmi_lan.conf

---

🧚 SEE ALSO 🧚

ipmi_lan(5), ipmi_ui(1), openipmish(1)

---

👑 KNOWN PROBLEMS 👑

Currently, ipmilan does not implement writing the config file 😭 IPMI commands to change configuration options are accepted, but the permanent writing of the changes does not currently work. So like, the vibes are stored... in the moment. Not on disk. iykyk 💀

---

💐 AUTHOR 💐

Corey Minyard <cminyard@mvista.com>

---

and that's the whole page bestie 🫶 this was ipmilan(8) from OpenIPMI, dated 06/26/12 — go forth and configure responsibly, mwah 💖✨