Timeline for Should changing firewall settings to block all interrupt ongoing ssh session
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2022 at 2:28 | history | became hot network question | |||
| Aug 7, 2022 at 20:36 | vote | accept | ahron | ||
| Aug 7, 2022 at 19:26 | answer | added | thrig | timeline score: 7 | |
| Aug 7, 2022 at 18:51 | comment | added | ilkkachu |
or clear all or some of the states with pfctl -F states or pfctl -k, I guess. (based on the pfctl man page and the docs). I don't really know about pf so I'm not sure I dare post this as an answer...
|
|
| Aug 7, 2022 at 18:40 | comment | added | ahron | Ah, the state does the trick. Thanks! | |
| Aug 7, 2022 at 18:39 | comment | added | ilkkachu |
pf looks to have something similar, by default, the man page says: "By default pf(4) filters packets statefully; the first time a packet matches a pass rule, a state entry is created; for subsequent packets the filter checks whether the packet matches any state. If it does, the packet is passed without evaluation of any rules."
|
|
| Aug 7, 2022 at 18:38 | comment | added | ilkkachu | if you block all traffic, then yes, it should block your existing connection too. (It should hang, not break, at least not immediately.) But e.g. with iptables on Linux, it's rather common to accept established connections early in the ruleset, and only do detailed checking on new connections. | |
| Aug 7, 2022 at 18:27 | history | asked | ahron | CC BY-SA 4.0 |