RN2NCID.CONF(5)

🌸 rn2ncid.conf — the configuration file for rn2ncid 💅

okay bestie, so this is the manual for rn2ncid.conf, section 5 of the NCID manuals. it's the little config file that tells rn2ncid how to behave. let's get into it ✨

---

✨ NAME ✨

rn2ncid.conf — the configuration file for rn2ncid 🎀

---

💖 DESCRIPTION 💖

so like, the rn2ncid.conf file is where all the configuration info for rn2ncid lives. it's giving "settings menu but make it a text file" fr fr.

here's the thing — rn2ncid.conf only understands 3 types of lines, and honestly? iconic minimalism:

• a blank line — ignored. it's just vibing. we don't see it. 🙈
• a comment line, beginning with # — also ignored. it's journaling, not instructions. 💅
• VARIABLE = VALUE — the actual tea ☕. and heads up: VALUE can contain spaces if it is between quotes.

peep rn2ncid.conf itself for all the default values — that's where the defaults live, bestie 👑

---

🦋 VARIABLES 🦋

here's the full lineup, no skips, no cuts:

• verbose = level — level is in the range 1-9. lowkey important: not all verbose levels are used. so don't come for me if 7 does nothing 🫶
• HostnameFlag = value — value is 0 or 1. if it's 1, the hostname gets included in the IDENT string. periodt.
• ncidaddr = host address — the NCID server host address. can be an IP address or a resolvable host name. flexible queen 💅
• ncidport = port — the NCID server port number. that's it, that's the whole job.
• delay = seconds — if the connection to the NCID server gets lost 😭, this is how many seconds you wait between reconnection attempts. patience is a virtue ig.
• cellport = port — the listen port, exactly as specified in the Remote Notifier application. don't freestyle this one, match it up ✨
• reject = from address[,from address][,from address]... — okay so SMS and MMS messages usually have a 'from' address, and depending on the carrier that could be a number or an email address. you give it a comma separated list of addresses that will NOT be transmitted by the NCID server to all listening NCID clients. why, you ask? because this is what stops endless loops — and endless loops could result in excessively high data or text charges by your cell phone carrier 💀💸 protect your wallet, bestie.

Remote Notifier sends the 'from' address in its 'data' (fifth) field. see NOTES below for the full breakdown 👇

so here's an example of what an endless loop would look like, and it's genuinely terrifying:

• cell phone gets SMS
• Remote Notifier sends out the SMS
• rn2ncid gets the SMS and sends it to the NCID server as 'MSG'
• the ncid-page module gets this 'MSG' and forwards it back to the cell phone
• cell phone gets the 'MSG' as an SMS
• cycle repeats forever 🔁😭

to prevent this endless loop, suppose you have ncid-page.conf configured to send SMS messages to your cell 'from' your email address of:

johndoe@yahoo.com

then you might want to set 'reject' to be:

reject = johndoe@yahoo.com

and boom 💥 loop broken. main character energy.

---

🌈 NOTES 🌈

Remote Notifier sends six pieces of information — a whole six-course meal, no cap:

1. version (e.g., 'v2')
2. unique device id in hex
3. unique notification id in hex
4. event type (BATTERY, PING, SMS, etc.)
5. data (terse information)
6. event contents (verbose free-form text, can be multi-line)

---

⭐ EXAMPLES ⭐

set the NCID server IP address:

ncidaddr = 192.168.1.20

set the Remote Notifier listen port:

cellport = 10600

reject SMS/MMS messages to manage text blocking:

reject = 9999

---

🫶 SEE ALSO 🫶

• rn2ncid.1

---

and that's the whole page, bestie, you ate it up 🍓✨ this one came from the NCID crew, dated 2022-11-8 — go forth and configure responsibly 💜👑