NFD-AUTOREG(1)

👑 NFD-AUTOREG(1) — nfd-autoreg 💅

okay so before we even start: this page lives in the Named Data Networking Forwarding Daemon (NFD) manual, and it's about nfd-autoreg, the automatic prefix registration daemon. she's lowkey the most helpful little background app you'll ever meet, fr fr. 🦋

---

✨ NAME ✨

nfd-autoreg — NFD automatic prefix registration daemon

like… she registers prefixes for you. automatically. main character energy honestly. 🎀

---

🌸 SYNOPSIS 🌸

nfd-autoreg [-i|--prefix prefix]... [-a|--all-faces-prefix prefix]...
  [-b|--blacklist network]... [-w|--whitelist network]... [-c|--cost cost]
nfd-autoreg -h|--help
nfd-autoreg -V|--version

(and yes bestie, -a/--all-faces-prefix is in the synopsis up there — the OPTIONS section below just doesn't describe it, so I'm not gonna make stuff up about it 🙈 iykyk)

---

💖 DESCRIPTION 💖

nfd-autoreg is a daemon application that automatically registers the prefix(es) you specify when new on-demand faces get created. translation: when a new UDP face pops into existence as the result of an incoming packet, or when a new TCP face shows up as the result of an incoming connection — that's when she does her thing. no cap, she's just sitting there waiting to be useful. ⭐

---

🎀 OPTIONS 🎀

• -i <prefix>, --prefix <prefix> — the prefix that should get automatically registered when a new remote face is created ✨. you can repeat this multiple times to specify additional prefixes — stack 'em up, she can handle it.
• -b <network>, --blacklist <network> — a blacklisted network, e.g. 192.168.2.32/30 or ::1/128 🚫. can be repeated multiple times to specify multiple blacklisted networks. the prefixes will be auto-registered only when the remote IP address is NOT inside the specified range(s), but IS inside the range defined by the whitelist(s), if any. default: none.
• -w <network>, --whitelist <network> — a whitelisted network, e.g. 192.168.2.0/24 or ::1/128 ✅. can be repeated multiple times to specify multiple whitelisted networks. the prefixes will be auto-registered only when the remote IP address is inside the specified range(s), excluding any blacklisted range(s). default: 0.0.0.0/0 and ::/0.
• -c <cost>, --cost <cost> — the RIB cost to assign to auto-registered prefixes. if you don't specify it, the cost is set to 255. that's the default, bestie, she said so 💅.
• -h, --help — print the help message and exit. your girl is helpful like that 🫶.
• -V, --version — show version information and exit. slay.

---

🦋 EXIT STATUS 🦋

• 0 — no error. we love a clean exit ✨
• 1 — an unspecified error occurred 😭 (vague, ominous, iconic)
• 2 — malformed command line, e.g. invalid, missing, or unknown argument 💀 (check your flags, bestie)
• 4 — insufficient privileges 🙈 (you need more power for this one)

---

🌈 EXAMPLES 🌈

nfd-autoreg -i /app1/video -i /app2/pictures -b 10.0.0.0/8

auto-register two prefixes — /app1/video and /app2/pictures — for any newly created on-demand faces, except the ones that have their remote IP address in the 10.0.0.0/8 network. obsessed. two prefixes, one blacklist, zero stress 🔥

---

💜 Copyright 💜

Copyright © 2014-2024 Named Data Networking Project.

---

and that's the whole page, bestie 🫶 version 24.07, dated 1980-01-01, straight out of the Named Data Networking Forwarding Daemon (NFD) manual set — go forth and auto-register responsibly 💅🎀