ifup(8)

๐Ÿ’… ifup(8) โ€” the System Manager's Manual, but make it make sense โœจ

okay so bestie, quick vibe check: this is the manual page for ifup, living in section 8 of the System Manager's Manual. it's the little gremlin that brings your network interfaces up. let's get into it ๐Ÿซถ


๐ŸŒธ NAME ๐ŸŒธ

ifup โ€” bring interfaces up. that's it, that's the whole job. main character energy fr ๐Ÿ’…

โœจ SYNOPSIS โœจ

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

you pass it some options (maybe), and then the interfaces you want to wake up. iconic.

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

ifup is the one that actually configures interfaces, okay? and it does it according to how they are configured in the configuration database โ€” so it's not out here improvising, it's reading the config db and following instructions like a good little soldier. periodt ๐Ÿ’œ

๐ŸŽ€ OPTIONS ๐ŸŽ€

  • -a, --auto โ€” only matches interfaces that are marked as auto. like, only the ones who volunteered ๐Ÿ’–
  • -f, --force โ€” forces configuration of the interface. ngl this option literally exists for compatibility with other implementations, so it's giving "i'm here because my friends are here" ๐Ÿ˜ญ
  • -h, --help โ€” displays supported options to ifquery. yep, that's what it says. not to ifup, to ifquery. we don't make the rules, we just report them ๐Ÿ™ˆ
  • -i, --interfaces FILE โ€” uses FILE as the config database. your config, your rules โœจ
  • -n, --no-act โ€” shows you what commands would be run instead of actually running them. lowkey the best option for testing configuration changes without the consequences ๐Ÿ’€ super useful, no cap.
  • -v, --verbose โ€” shows you what commands are being run as they're being executed. narrating the whole thing, love that for us ๐ŸŒˆ
  • -E, --executor-path PATH โ€” looks for executors in the given PATH. go find your people, bestie ๐Ÿงš
  • -I, --include PATTERN โ€” includes PATTERN when matching against the config or state database ๐Ÿ“
  • -L, --no-lock โ€” does not use a lockfile to serialize state changes. highkey risky if you've got stuff running at the same time, just so you know ๐Ÿ‘€
  • -S, --state-file FILE โ€” uses FILE as the state database ๐Ÿ’–
  • -T, --timeout TIMEOUT โ€” waits up to TIMEOUT seconds for executors to complete before raising an error. patience is a virtue but it's also finite โณ๐Ÿ”ฅ
  • -V, --version โ€” prints the ifupdown-ng version and exits. bye bestie ๐Ÿ‘‹
  • -X, --exclude PATTERN โ€” excludes PATTERN when matching against the config or state database. not you, not you, definitely not you ๐Ÿ™…โ€โ™€๏ธ

๐Ÿ‘‘ SEE ALSO ๐Ÿ‘‘

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

go read those too, they're literally the rest of the lore ๐Ÿ“šโœจ

๐Ÿ’œ AUTHORS ๐Ÿ’œ

Ariadne Conill <ariadne@dereferenced.org> โ€” an absolute icon, we stan ๐ŸŒŸ


ok that's the whole page, no cap. every flag, every default, every path, all of it. you're welcome ๐Ÿ’…

and a cute little sign-off for the footer bestie: this one's from the System Manager's Manual, dated 2026-05-10, and yes โ€” that's the source/version and date, preserved with love ๐ŸŽ€๐Ÿ’– slay.

๐Ÿ“ฆ where this page comes from