mirror of
https://github.com/3proxy/3proxy.git
synced 2026-11-22 23:59:41 +08:00
mark <number> extends the allow or deny rule above it, as nolog and weight do: a connection the rule lets through carries the mark on its outgoing sockets, towards the destination and towards the parents, so policy routing and firewall rules can tell its packets apart (SO_MARK of Linux, SO_USER_COOKIE of FreeBSD; on a system with no mark the command sets it to nothing). The UDP sockets of a session towards a destination are marked the same, the SOCKS UDP ASSOCIATE relays among them, for the rule that let the session through is looked up for each destination. A mark with no rule above it, or not a number, is refused.