firehol-server(5)

📦
version 3.1.8 · 4 versions
, in debian trixie, ubuntu resolute, ubuntu stonking

💖 firehol-server(5) — the server & route glow-up 💖

okay bestie, sit down, hydrate, because we're talking about firehol-server from the FireHOL reference, version 3.1.8. this is the page that tells you how to open a door for people knocking on your box. it's giving hostess energy. 🎀

✨ NAME ✨

firehol-server — server, route commands: accept requests to a service 🌸

✨ SYNOPSIS ✨

{ server | server46 } service action rule-params

server4 service action rule-params

server6 service action rule-params

{ route | route46 } service action rule-params

route4 service action rule-params

route6 service action rule-params

like. that's the whole vibe. pick your flavor, plug in your service, pick your action, sprinkle params. 💅

✨ DESCRIPTION ✨

so the server subcommand is literally you declaring "yes, this service is welcome here" — either on an interface or a router. and here's the cute part: any rule-params you handed to a parent interface or router? the server inherits them. generational wealth but for firewall rules. 🫶

for FireHOL, a server is the destination of a request. and yes, some multi-socket services are messier than that conceptually, but FireHOL keeps it simple: a server always accepts requests. no cap. ✨

route is just server wearing a little disguise — it's an alias for server and it can only be used in routers. not interfaces. routers only, bestie. 🚫

the service parameter is one of the supported service names from firehol-services(5). and you can flex multiple of them — just space delimit them inside quotes. 🦋

the action can be any of the actions listed in firehol-actions(5). go off.

and the rule-params define a set of rule parameters that further restrict the traffic matched to this service. more deets live in firehol-params(5). 👑

Note 📝 writing server4 is exactly equivalent to writing ipv4 server, and it makes sure this subcommand only applies in the IPv4 firewall rules. writing server6 is exactly equivalent to writing ipv6 server, and it makes sure this subcommand only applies in the IPv6 firewall rules. writing server46 is equivalent to writing both server and ensures this subcommand applies in both the IPv4 and IPv6 firewall rules. it cannot be used as part of an interface or router that is IPv4 or IPv6 only. so don't try it, it's not that girl in that context. 💀 the default server inherits its behaviour from the enclosing interface or router. and the same rules apply to the variations of route. yes, all of them. 🎀

✨ EXAMPLES ✨

here's the tea, copied exactly, no notes: 🍓

server smtp accept

server "smtp pop3" accept

server smtp accept src 192.0.2.1

server smtp accept log "mail packet" src 192.0.2.1

look at that. simple. iconic. ate. 💅✨

✨ SEE ALSO ✨

go read them all, they're all bangers, iykyk 📚💜

✨ AUTHORS ✨

FireHOL Team. 👑

and that's the whole page, bestie!! built 13 Apr 2025 for the FireHOL Reference, version 3.1.8. mwah, go configure something gorgeous 🫶💖✨🌈

📦 where this page comes from