10 ms·
I'm not in favor of doing it, but you pick up some benefits in some cases. For TCP, if your server doesn't deal well with bogus packets, having a stateful fire
by toast0 3y ago
I'm not in favor of doing it, but you pick up some benefits in some cases.
For TCP, if your server doesn't deal well with bogus packets, having a stateful firewall allows dropping data packets without an associated connection. Stateful firewalls may have syncookies where your server os doesn't, in case you're running 20 year old servers or macos servers.
For UDP servers, it could be potentially useful if the rate limiting in the firewall is more flexible than in the server application. But for DNS, usually you're looking at one request -> one response, I don't know why you would want a state for that.
Of course, it is useful to mix stateful and stateless: allow all the service related traffic without state, but allow for incidental outbound traffic with state. Drop everything else. But that's really more about having a clear access control layer than protecting a host from network abuse.