Summary: | pfctl: warning: namespace collision with <bruteforce> global table | ||
---|---|---|---|
Product: | Base System | Reporter: | Matteo Riondato <matteo> |
Component: | conf | Assignee: | freebsd-pf (Nobody) <pf> |
Status: | New --- | ||
Severity: | Affects Some People | CC: | kp |
Priority: | --- | Keywords: | security |
Version: | CURRENT | ||
Hardware: | Any | ||
OS: | Any |
Description
Matteo Riondato
2022-03-02 13:25:41 UTC
Actually, it seems that the namespace collision warning also happens with a pf.conf that does not use anchors and contains table <bruteforce> persist block log quick from <bruteforce> pass in proto tcp from any to ($interface) port ${tcp_services} keep state \ (max-src-conn 10, max-src-conn-rate 1/4, \ overload <bruteforce> flush global) This set of rules is inspired by the very similar one from https://www.openbsd.org/faq/pf/filter.html#stateopts, thus one would expect it to work. Some more investigation: it turns out that the problem is more subtle than I thought. My previous examples of pf.conf were "slimmed down" versions of what I actually tried. The following does not work: table <bruteforce> persist block log quick from <bruteforce> label "bruteforceblock" pass in proto tcp from any to ($interface) port ${tcp_services} keep state \ (max-src-conn 10, max-src-conn-rate 1/4, \ overload <bruteforce> flush global) The following works: table <bruteforce> persist block log quick from <bruteforce> label "mybruteforceblock" pass in proto tcp from any to ($interface) port ${tcp_services} keep state \ (max-src-conn 10, max-src-conn-rate 1/4, \ overload <bruteforce> flush global) The only difference is the label in the block rule. Actually, it is even weirder. Sometimes it works, sometimes it doesn't. I'm confused, at this point. |