ovpn_peer_vp...dr_conflict6(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay so bestie, this page is from the Kernel API Manual (section 9, kernel-space functions only, we're fancy like that ✨) and it's all about ovpn_peer_vpn_addr_conflict6 β€” the little function that checks whether a VPN v6 address is already being used by somebody else. no cap, that's the whole job πŸŽ€


✨ SYNOPSIS ✨

bool ovpn_peer_vpn_addr_conflict6 (struct ovpn_priv *ovpn , const struct ovpn_peer *peer , const struct in6_addr *addr );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ovpn β€” the openvpn instance we're snooping around in πŸ”
  • peer β€” the peer that's being added or updated, or NULL (yes, NULL is a whole vibe here, it's allowed)
  • addr β€” the VPN IPv6 address we wanna check, bestie πŸ’–

🌸 DESCRIPTION 🌸

so basically, this function checks whether addr is already assigned to another peer. like, is this address taken? because we do NOT do duplicates in this house πŸ’…

the peer argument gets ignored when a match is found β€” which is literally the point, because it means peer updates can keep an existing address without the function throwing a fit 😌 slay.

and unspecified addresses? ignored. not our problem, not our drama πŸ™ˆ

πŸ‘‘ NOTE πŸ‘‘

okay bestie this one's important: the caller must hold ovpn->lock. like, no lock, no service. don't come for this function without it, fr fr πŸ”’

⭐ RETURN ⭐

  • true on conflict πŸ”₯ (the address is taken, oops)
  • false otherwise 🧚 (you're good, go off)

🌈 SEE ALSO 🌈

the whole squad, gathered for you πŸ’œ β€” straight from the kernel file ./drivers/net/ovpn/peer.c:


and that's the page, bestie!! 🫢 this lil manpage lives in ./drivers/net/ovpn and it's dated October 2026 β€” yes, from the future, main character energy only πŸ’€βœ¨ mwah, go check those addresses, ily πŸŽ€

πŸ“¦ where this page comes from