MASON(1)

πŸ“¦ version 1.0.0, in debian bookworm, ubuntu jammy

✨ mason β€” like, the manual πŸ’…

okay so bestie, <pink>mason</pink> is a whole queen and this page is her little intro. it's MASON(1), she lives in section 1 of the manual, and she is here to help you build a firewall interactively, which is genuinely iconic of her.


🌸 NAME 🌸

mason β€” interactively create a firewall 🫢


πŸ¦‹ SYNOPSIS πŸ¦‹

mason < logfile > rulefile

πŸ’– DESCRIPTION πŸ’–

okay so real talk: this manual page is just a brief lil rundown of the mason command. not the whole novel, just the vibes. πŸ“–βœ¨

mason interactively generates a set of firewall rules for a Linux-based firewall. and the way she does it?? absolute main character behavior:

  • turns on full IP logging πŸ”₯
  • watches the logs for connections πŸ‘€
  • generates rules describing the connections she saw ✨

she's also lowkey familiar with most of the quirks of various connection types (think ftp and IRC β€” the messy ones, you know the ones), and she can output rules for 2.0.x ipfwadm, 2.2.x ipchains, and Cisco packet filters. versatile queen. πŸ‘‘

so how does she actually operate? mason reads log file info from standard input and writes firewall rules to standard output. that means she can work offline, or on a completely separate system. no cap. 🫢 and if you want real-time firewall generation?? you can do it with a command like tail(1). slay.

ngl, most users are gonna wanna run mason with a user-friendly interface like mason-gui-text(1). just saying. πŸŽ€

🌈 ENVIRONMENT 🌈

mason gets configured through these environment variables. yes bestie, she's that kind of girl.

  • ECHOCOMMAND β€” sets the type of firewall rules that mason should output to standard out. allowed values include "ipfwadm" and "ipchains". by default, mason outputs whatever kind of rules are supported by the currently running Linux kernel. πŸ’…
  • DOCOMMAND β€” sets the type of firewall rules that mason should run immediately when a rule is generated. allowed values include "ipfwadm" and "ipchains". by default, mason outputs whatever kind of rules are supported by the currently running Linux kernel. πŸ‘‘
  • HEARTBEAT β€” if you set this to "yes", mason will output a "+" or "-" to standard error whenever a rule generated by mason has been triggered. it's giving pulse check πŸ«€
  • DYNIP β€” set this to the list of interfaces that have dynamically assigned addresses, separated by spaces. (yes, spaces. don't be weird about it.) 🌸

πŸ‘€ SEE ALSO πŸ‘€


πŸ’œ AUTHOR πŸ’œ

this manual page was written by Jeff Licquia <jeff@luci.org>, for the Debian GNU/Linux system (but may be used by others). we stan a generous king. πŸ™ˆπŸ’–


and that's the whole thing bestie β€” no more notes, no more pages, we're at the footer which literally just says MASON(1) again like a lil bow on top of the whole package. πŸŽ€ so consider this your cute lil sign-off, from section 1 with love. bye pookie, go build that firewall πŸ’…βœ¨πŸ¦‹

πŸ“¦ where this page comes from