ifquery(8)

๐Ÿ’… ifquery(8) โ€” like, the manual, but make it make sense ๐Ÿซถ

okay bestie, so this page is ifquery(8) from the System Manager's Manual โ€” yes, the section 8 one, the admin-y one, not some random section 1 situation. we're gonna go through it together and you're gonna get it. ๐ŸŽ€


โœจ NAME โœจ

ifquery โ€” query interface configuration and state. it's giving "detective but for your network interfaces" ๐Ÿ”๐Ÿ’–


โœจ SYNOPSIS โœจ

ifquery [<options>...] <interfaces...>

ifquery -L|--list

ifquery -s|--state

three whole moods, no cap. either you're querying specific <interfaces...> with some <options>..., or you're doing the -L|--list thing, or you're doing the -s|--state thing. pick your fighter ๐Ÿ’…


๐ŸŒธ DESCRIPTION ๐ŸŒธ

so ifquery is the girl who goes into your interface configuration file and pulls the info out for you. that's her job. that's her whole personality.

she can also convert from old versions of the interface configuration file to the current format โ€” like a glow-up for your config, honestly iconic. ๐Ÿ”ฅ


๐Ÿฆ‹ OPTIONS ๐Ÿฆ‹

  • -a, --auto โ€” only match interfaces that are marked as auto. like a VIP list, but for interfaces. โœจ
  • -h, --help โ€” shows you all the supported options for ifquery. the "who, what, when, where" of it all. ๐Ÿ™ˆ
  • -i, --interfaces FILE โ€” use FILE as the config database. you're telling her "hey, this is the file, not the usual one." ๐Ÿ—‚๏ธ
  • -p, --property PROPERTY โ€” prints the values of matching properties for an interface. very "give me the receipts" of her. ๐Ÿงพ
  • -r, --running โ€” prints the interface names that are marked as running in the state database. the ones that actually showed up to the party. ๐Ÿ‘‘
  • -s, --state โ€” query the state database instead of the config database. different database, different vibe check. ๐ŸŒˆ
  • -D, --dot โ€” generates a dependency graph that can be used with GraphViz dot(1). used with --list. very aesthetic, very "look at the little arrows." ๐Ÿ“Š
  • -I, --include PATTERN โ€” include PATTERN when matching against the config or state database. if she matches, she's in. ๐Ÿ’–
  • -L, --list โ€” list interfaces which exist in the configuration database. the roster. the lineup. the cast list. โญ
  • -P, --pretty-print โ€” when listing interfaces, prints their configuration in a format that's compatible with interfaces(5) files. yes, she formats it. yes, it's gorgeous. ๐ŸŽ€
  • -U, --allow-undefined โ€” creates virtual interfaces for any interfaces not explicitly defined in the configuration file. this is primarily useful for property queries. lowkey the wildcard option, honestly. ๐Ÿƒ
  • -S, --state-file FILE โ€” use FILE as the state database. for when the state database is somewhere else and you're like "not me having to point at it." ๐Ÿ“
  • -T, --timeout TIMEOUT โ€” wait up to TIMEOUT seconds for executors to complete before raising an error. patience: measurable. โณ
  • -V, --version โ€” prints the ifupdown-ng version and exits. she tells you who she is and then leaves. main character energy. ๐Ÿ’€
  • -X, --exclude PATTERN โ€” exclude PATTERN when matching against the config or state database. the "you're not on the list" option. ๐Ÿšซ
๐Ÿ’€ real talk though: -T/--timeout means it waits, and if the executors don't finish in time it raises an error. so don't set it to something tiny and then act surprised, bestie.

๐Ÿ‘€ SEE ALSO ๐Ÿ‘€

the whole friend group, fr fr. ๐Ÿซถ


๐ŸŒŸ AUTHORS ๐ŸŒŸ

Ariadne Conill <ariadne@dereferenced.org> โ€” the icon who made this happen. bow down. ๐Ÿ‘‘


and that's the page!! cute lil sign-off: this one's from ifupdown-ng, dated 2026-05-10, and it will forever be ifquery(8). go query something, you got this ๐Ÿ’œ๐Ÿฆ‹๐ŸŒธ

๐Ÿ“ฆ where this page comes from