RTLABEL_ID2NAME(9)

🌸 NAME 🌸

okay so this is the RTLABEL_ID2NAME(9) page from the Kernel Developer's Manual, and we're talking about rtlabel_id2name, rtlabel_id2sa, rtlabel_name2id, and rtlabel_unref — the girlies that manipulate route labels. periodt. 💅

✨ SYNOPSIS ✨

#include <sys/types.h>
#include <sys/socket.h>
#include <net/route.h>

const char *
rtlabel_id2name(u_int16_t id);

struct sockaddr *
rtlabel_id2sa(u_int16_t labelid, struct sockaddr_rtlabel *sa_rl);

u_int16_t
rtlabel_name2id(char *name);

void
rtlabel_unref(u_int16_t id);

💅 DESCRIPTION 💅

Route labels are arbitrary data appended to route entries, and they can be acted upon by pf(4). no cap, that's the vibe. ✨

🎀 rtlabel_name2id(char *name) 🎀

Return the numerical ID of the route label named name, and create the label if it does not already exist. slay, it's giving "make it if it's not there." 💖

🦋 rtlabel_id2name(u_int16_t id) 🦋

Return the string name of the route label with ID id. iconic lookup behavior, honestly. 🌈

🍓 rtlabel_id2sa(u_int16_t labelid, struct sockaddr_rtlabel *sa_rl) 🍓

Populate sa_rl with the data from the route label specified by labelid. yes bestie, fill it in. 🫶

💜 rtlabel_unref(u_int16_t id) 💜

Remove a reference to the route label with ID id, and free the label if the reference count drops to 0. that's the cleanup girlie. 🧚

🦋 CONTEXT 🦋

rtlabel_id2name(), rtlabel_id2sa(), rtlabel_name2id(), and rtlabel_unref() can be called during autoconf, from process context, or from interrupt context. so flexible, lowkey obsessed. 💅

🎀 RETURN VALUES 🎀

rtlabel_name2id() returns 0 if it was unable to create a route label. if it can't create one, you get 0 back — noted, bestie. 💖

🔥 SEE ALSO 🔥

• route(4)
• route(9)

---

mwah 💋 cute lil sign-off: this is Debian realness, dated October 15, 2014, serving RTLABEL_ID2NAME(9) energy. bye bestie! 🫶✨