PINGU.CONF(5)

πŸ“¦ version 1.5.1, in alpine 3.22, alpine 3.23, alpine 3.24

πŸ’– NAME πŸ’–

Okay so bestie, this is pingu.conf β€” the configuration file for the pingu daemon, and yes, you're reading the pingu.conf(5) manual page. Buckle up, it's giving config-file main character energy πŸ’…βœ¨

🌈 DESCRIPTION 🌈

The file can contain 3 different contexts: Global context, interface context and host context. Iconic, honestly.

Blank lines and lines starting with # are ignored β€” literally just skip them, no cap πŸ™ˆ

✨ GLOBAL CONTEXT ✨

The config file starts in global context. In this section the default values for the keywords used in interface and host sections are set. Values set in global context can be overridden in interface and host sections. So global is like the vibe-setter, and the other sections can absolutely do their own thing 🫢

  • interval β€” set the default ping burst interval.
  • timeout β€” the default ping timeout value in seconds. If the ping response does not come back within timeout seconds the ping is considered lost.
  • required β€” the minimum required ping responses of a burst to consider the host online.
  • retries β€” maximum sent ping packets for a burst.
  • up-action β€” the default action to execute when a ping host goes online.
  • down-action β€” the default action to execute when a ping host goes offline.

πŸ¦‹ INTERFACE CONTEXT πŸ¦‹

Example first, because visuals matter:

interface eth0 {
        keyword value
        ...
}

The keywords valid in an interface section are:

  • gateway-down-action β€” execute this action when a gateway is considered offline.
  • gateway-up-action β€” execute this action when a gateway is considered online.
  • label β€” a user defined label that will be used in logs and by pinguctl.
  • load-balance β€” enable balancing for this interface. A minimum of two interfaces need to be configured in order for load-balancing to work. An optional weight value can be given.
  • required-hosts-online β€” the minimum number of ping hosts that needs to be online to consider the gateway online.
  • route-table β€” the alternate route table for this interface.
  • rule-priority β€” the preference value for the ip rule.
  • ping β€” host to ping to verify that gateway is still up. This is the same as defining a host and bind it to interface.
  • fwmark β€” add an additional route rule for configured fwmark integer.
Heads up bestie: load-balance is not a solo act β€” a minimum of two interfaces need to be configured in order for load-balancing to work, and an optional weight value can be given. Periodt πŸ’€

πŸŽ€ HOST CONTEXT πŸŽ€

Example time again:

host 1.2.3.4 {
        keyword value
        ...
}
  • bind-interface β€” bind the pings to this interface.
  • down-action β€” execute this action when ping host goes offline.
  • interval β€” the interval for ping bursts.
  • label β€” a label to be used in logs and pinguctl.
  • required β€” the number of required ping responses to consider host online.
  • retry β€” the maximum number of retries for a ping burst.
  • timeout β€” the ping response timeout value in seconds. If no ping response returns within this value the ping is considered lost.
  • up-action β€” execute this action when a ping host goes online

πŸ‘‘ AUTHORS πŸ‘‘

Natanael Copa 🌟


Alright bestie, that's the whole page. The footer girly says 01/03/2025, and this is the pingu.conf(5) manual β€” go configure your daemon and slay βœ¨πŸ’…

πŸ“¦ where this page comes from