firehol-client(5)

πŸ“¦
version 3.1.8 Β· 4 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

πŸ’– firehol-client(5) β€” the client subcommand, bestie edition πŸ’–

okay so this is the manual page for firehol-client, aka the client command, from the FireHOL fam (version 3.1.8, if you're keeping receipts). it's giving "short page, big power" and i'm obsessed. let's get into it ✨


🌸 SYNOPSIS 🌸

{ client | client46 } service action [rule-params]

client4 service action [rule-params]

client6 service action [rule-params]

like. look at her. three whole ways to say the same cute thing. periodt πŸ’…


πŸ¦‹ DESCRIPTION πŸ¦‹

so the client subcommand defines a client of a service on an interface or a router. that's the whole job. she's focused.

here's the little plot twist tho: any rule-params you hand to a parent interface or router get inherited by the client β€” but reversed. the vibes flip. it's giving inheritance with a plot twist πŸ™ˆ

for FireHOL, a client is the source of a request. yes, some multi-socket services make this messier than a group chat at 2am, but to FireHOL it's simple: a client always initiates the connection. main character energy, always making the first move. no cap.

the service parameter is one of the supported service names from firehol-services(5). and you can absolutely specify multiple services β€” space delimited, wrapped in quotes. slay.

the action can be any of the actions listed in firehol-actions(5). go wild, but like, responsibly.

the rule-params define a set of rule parameters that further restrict the traffic matched to this service. more details live in firehol-params(5) if you wanna go deeper.

Note πŸ“ writing client4 is equivalent to writing ipv4 client and ensures this subcommand is applied only in the IPv4 firewall rules. writing client6 is equivalent to writing ipv6 client and ensures this subcommand is applied only in the IPv6 firewall rules. writing client46 is equivalent to writing both client and ensures this subcommand is applied in both the IPv4 and IPv6 firewall rules; it cannot be used as part an interface or router that is IPv4 or IPv6 only. so like, don't try it. she will not cooperate 😭 the default client inherits its behaviour from the enclosing interface or router. she's a nepo baby but in a cute way πŸ’–

✨ EXAMPLES ✨

here's the whole mood board:

client smtp accept
client "smtp pop3" accept
client smtp accept src 192.0.2.1
client smtp accept log "mail packet" src 192.0.2.1

see how each one just adds a lil more seasoning? that's the journey. πŸ“


🌈 SEE ALSO 🌈

go read them all bestie, i'll wait πŸ’œ


πŸ‘‘ AUTHORS πŸ‘‘

FireHOL Team. iconic. no notes. πŸŽ€


and that's the page fr fr πŸ’… built by the FireHOL Reference, 13 Apr 2025, version 3.1.8 β€” mwah, go configure something gorgeous, love u bye πŸ¦‹βœ¨

πŸ“¦ where this page comes from