batadv_bla_check_claim(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ batadv_bla_check_claim β€” NAME ✨

okay so bestie, buckle up πŸ’… this page is batadv_bla_check_claim(9) from the Kernel API Manual, and it's literally just one little function asking one big question: is this address claimed or not? that's it. that's the whole vibe. πŸŽ€


🌸 SYNOPSIS 🌸

bool batadv_bla_check_claim (struct batadv_priv *bat_priv , u8 *addr ,
unsigned short vid );

she returns a bool, she takes three things, and she does not elaborate. main character energy honestly πŸ‘‘


πŸ¦‹ ARGUMENTS πŸ¦‹

  • bat_priv β€” the bat priv holding all the mesh interface information. it's the whole info vault babes, everything about the mesh lives in here πŸ—‚οΈ
  • addr β€” the mac address whose claim status we're checking. yes, that mac address. the one under investigation πŸ”
  • vid β€” the VLAN ID. don't skip her, she matters 🫢

πŸ’œ DESCRIPTION πŸ’œ

so what's actually going down: addr gets checked to see if this address is claimed by the local device itself. that's the whole bit. she's checking whether the device is like "yeah that's mine" or whether somebody else out here is claiming it 😭

no cap, that's it. short function, clear purpose, iconic behavior ✨


🌈 RETURN 🌈

she gives you back one of two answers, and please read them carefully because they are not symmetrical, bestie:

  • true β€” if bla is disabled, or the mac is claimed by the device βœ…
  • false β€” if the device addr is already claimed by another gateway πŸ’€
ngl the false case is the spicy one β€” another gateway has already planted its flag on this address, so the vibe check has officially failed 😬

πŸ’– SEE ALSO πŸ’–

the kernel file lives right here: ./net/batman-adv/bridge_loop_avoidance.c β€” that's where the whole bridge-loop-avoidance saga unfolds (yes, that's what the bla is, the file name literally spoils it 🫣).

and now, the entire friend group, in order, no one left out, periodt:

batadv_choose_claim(9), batadv_choose_backbone_gw(9), batadv_compare_backbone_gw(9), batadv_compare_claim(9), batadv_backbone_gw_release(9), batadv_backbone_gw_put(9), batadv_claim_release(9), batadv_claim_put(9), batadv_claim_hash_find(9), batadv_backbone_hash_find(9), batadv_bla_del_backbone_claims(9), batadv_bla_send_claim(9), batadv_bla_loopdetect_report(9), batadv_bla_get_backbone_gw(9), batadv_bla_update_own_backbone_gw(9), batadv_bla_answer_request(9), batadv_bla_send_request(9), batadv_bla_send_announce(9), batadv_bla_add_claim(9), batadv_bla_claim_get_backbone_gw(9), batadv_bla_del_claim(9), batadv_handle_announce(9), batadv_handle_request(9), batadv_handle_unclaim(9), batadv_handle_claim(9), batadv_check_claim_group(9), batadv_bla_process_claim(9), batadv_bla_purge_backbone_gw(9), batadv_bla_purge_claims(9), batadv_bla_update_orig_address(9), batadv_bla_send_loopdetect(9), batadv_bla_status_update(9), batadv_bla_periodic_work(9), batadv_bla_init(9), batadv_bla_check_duplist(9), batadv_bla_check_ucast_duplist(9), batadv_bla_check_bcast_duplist(9), batadv_bla_is_backbone_gw_orig(9), batadv_bla_is_backbone_gw(9), batadv_bla_free(9), batadv_bla_loopdetect_check(9), batadv_bla_rx(9), batadv_bla_tx(9), batadv_bla_claim_dump_entry(9), batadv_bla_claim_dump_bucket(9), batadv_bla_claim_dump(9), batadv_bla_backbone_dump_entry(9), batadv_bla_backbone_dump_bucket(9), batadv_bla_backbone_dump(9)

like I said. the whole crew. go read them, they're all slaying in their own way πŸ’…βœ¨


and that's the page, bestie 🫢 sourced from ./net/batman-adv, dated October 2026, and officially filed under batadv_bla_check_claim(9) β€” go check those claims, and remember: if another gateway already claimed it, it's not yours, no matter how much you want it πŸ˜­πŸ’€πŸ“

πŸ“¦ where this page comes from