ENUM BATADV_HARD_IF_BCAST(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

enum batadv_hard_if_bcast β€” the broadcast-avoidance options, bestie πŸ’… (this one lives in the Kernel API Manual, so you already know it's kernel-business)


πŸ¦‹ SYNOPSIS πŸ¦‹

enum batadv_hard_if_bcast {
    BATADV_HARDIF_BCAST_OK ,
    BATADV_HARDIF_BCAST_NORECIPIENT ,
    BATADV_HARDIF_BCAST_DUPFWD ,
    BATADV_HARDIF_BCAST_DUPORIG

};

okay so that's the whole enum, all four members, no cap β€” literally just vibes about whether a broadcast should actually go out on a given hard interface or not 🫢


πŸŽ€ Constants πŸŽ€

  • BATADV_HARDIF_BCAST_OK β€” bestie go ahead, do the broadcast on the according hard interface πŸ’– it's giving green light, main character energy, send it.
  • BATADV_HARDIF_BCAST_NORECIPIENT β€” broadcast not needed, because there's literally no recipient 😭 why are we yelling into the void, nobody's there.
  • BATADV_HARDIF_BCAST_DUPFWD β€” there is just the neighbor we got it from πŸ™ˆ so yeah, forwarding it back would be… a choice.
  • BATADV_HARDIF_BCAST_DUPORIG β€” there is just the originator πŸ‘‘ and only the originator. that's the whole guest list.

🌸 SEE ALSO 🌸

Kernel file ./net/batman-adv/hard-interface.h enum πŸ”₯ (yes, the header, go look at it, it ate)

Then the little friend group of related calls β€” all of these, exactly these, in this order, no skipping:

iykyk πŸ’œ


ngl this whole page is short and iconic, don't underestimate it β€” the details above are the entire thing, so don't go assuming extra members or behaviours that aren't written here πŸ™ˆ fr fr.

okay that's the whole page, mwah πŸ’‹ β€” brought to you by ./net/batman-adv 🌈 (that's the source/version, cutie) and dated October 2026 πŸŽ€, from the enum batadv_hard_if_bcast(9) manual page. slay, bye bestie πŸ‘‘βœ¨πŸ“

πŸ“¦ where this page comes from