IPSETCAT(1)

💖 IPSETCAT(1) 💖

okay bestie, welcome to ipsetcat, a certified icon from the libcorkipset library, manual section 1 (user commands, we're in the big leagues 🫶). she's a little CLI that lets you peek inside binary IP set files, and honestly? she's giving main character energy for such a small utility. let's get into it ✨

---

🌸 NAME 🌸

ipsetcat — utility of the libcorkipset library. that's it, that's the girl. 💅

---

🦋 SYNOPSIS 🦋

ipsetcat [options] <input filename>

one command, some options, one filename. lowkey the simplest situationship you'll ever be in. no cap. 🌈

---

🎀 DESCRIPTION 🎀

so what does she actually do? ipsetcat prints out the (non-sorted) contents of a binary IP set file. that's the whole job, and she does it flawlessly. ✨

bestie, note the non-sorted thing. it's not a bug, it's a lifestyle. more on that in a sec. 👑

---

💅 OPTIONS 💅

• <input filename> — the binary set file you want to read. that's the whole point of being here. if you wanna read from stdin instead, just pass - as the filename and she'll slurp it up like a strawberry milkshake 🍓.
• --output=<filename>, -o <filename> — writes the contents of the binary IP set file out to <filename>. if you don't give her this option, she just writes everything to standard output like a normal, well-adjusted program. 🫶
• --networks, -n — where possible, she groups the IP addresses in the set into CIDR network blocks. for dense sets this can greatly reduce the amount of output generated, which is a slay for your terminal and your eyeballs. 💖
• --verbose, -v — shows progress information about the files being read and written. if you don't pass this, the only output you'll get is any error messages that occur. so it's ✨quiet✨ unless something goes wrong. iconic behaviour honestly. 🌸
• --help — displays this help and exits. your girl is helpful like that. 💜

---

📝 Output format: 📝

the output will contain one IP address or network per line. simple. elegant. we love a consistent format. 🎀

if you give her the --networks option, then she'll collapse addresses into CIDR networks where possible. CIDR network blocks will have one of the following formats:

x.x.x.x/cidr
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/cidr

individual IP addresses will have one of the following formats:

x.x.x.x
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx

heads up bestie: we never include a /32 or /128 suffix for individual addresses, even if you've requested CIDR networks via the --networks option. so don't come for her about it. 💀

---

🚨 the unsorted thing 🚨

please note that the output is UNSORTED. there are no guarantees made about the order of the IP addresses and networks in the output. zero. none. she did not promise you alphabetical, she did not promise you numerical, she promised you content and she delivered. if you need it sorted, that's a you-and-sort problem, not hers. 😭

---

🌟 SEE ALSO 🌟

nah, nothing here, she's self-contained and unbothered. go read the libcorkipset docs if you're curious, iykyk. 💜

---

okay that's the whole page!! this manual page is from ipsetcat 1.1.1+git20171111.6842..., dated April 2024, and that's your girl's whole origin story. go read some IP sets, bestie. periodt. 💖✨🦋🎀