ifup(8)

✨ ifup — bring interfaces up ✨

okay bestie, listen up 💖 this is the ifup manual page from the System Manager's Manual section (that's section 8, the big-girl system administration one, iykyk). if you have ever needed to actually wake an interface up and make it exist in the world, this is literally the page for you. no cap.

---

🌸 NAME 🌸

ifup — bring interfaces up 🦋

---

🎀 SYNOPSIS 🎀

ifup [<options>...] <interfaces>

---

💅 DESCRIPTION 💅

ifup is the one that configures interfaces, obvi. the way it works is: it looks at how those interfaces are configured in the configuration database, and then it configures them to match. that's the whole vibe. ✨

it does not guess. it does not improvise. it reads the database, it does the thing. main character behaviour, honestly. 👑

---

🔥 OPTIONS 🔥

• -a, --auto — only match interfaces that are marked as auto. like, only the ones that signed up for it. 🫶
• -f, --force — force configuration of the interface. this one is highkey just here for compatibility with other implementations — it exists so other tools' vibes don't break. 💀
• -h, --help — display supported options to ifquery. yes, it says ifquery. that's what it says. we do not question it. 🙈
• -i, --interfaces FILE — use FILE as the config database. your config, your rules, bestie. 💖
• -n, --no-act — show what commands would be run instead of actually running them. absolute queen behaviour for testing configuration changes before you commit to the bit. ⭐
• -v, --verbose — show what commands are being run as they are executed. very "narrating my own life" energy, and honestly? iconic. ✨
• -E, --executor-path PATH — look for executors in the given PATH.
• -I, --include PATTERN — include PATTERN when matching against the config or state database. let it in. 🎀
• -L, --no-lock — do not use a lockfile to serialize state changes. > ⚠️ heads up: no lockfile means state changes aren't serialized anymore. if you're doing concurrent stuff, that's on you. 😭
• -S, --state-file FILE — use FILE as the state database.
• -T, --timeout TIMEOUT — wait up to TIMEOUT seconds for executors to complete before raising an error. give them a minute... but not, like, an unlimited minute. ⏳
• -V, --version — print the ifupdown-ng version and exit. slay, then dip. 💅
• -X, --exclude PATTERN — exclude PATTERN when matching against the config or state database. not you, girl. bye. 🌈

---

🦋 SEE ALSO 🦋

ifupdown-ng.conf(5) · ifdown(8) · ifquery(8) · interfaces(5)

---

👑 AUTHORS 👑

Ariadne Conill <ariadne@dereferenced.org>

---

and that's the whole page, bestie!! this version is from the System Manager's Manual, dated 2025-10-13, and it's the ifup(8) page in all its glory. go forth and bring those interfaces UP. 💖✨🌸🦋🎀💅