Timeline for Abort nftables port forwarding NAT flows
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 3, 2024 at 18:01 | comment | added | yawn | The original problem was killing existing NAT flows. This can be solved in at least two ways: filtering before connection tracking (raw priority) or filtering in forwarding. Digressing to stateless NAT did overload / stretch that question a bit, you're right! | |
| Mar 2, 2024 at 11:37 | comment | added | A.B | Your current questions shrugs off stateful NAT and goes on stateless NAT and then gets additional problems to solve. So is the initial problem described "I cannot kill existing flow by dropping elements from a map and / or adding a filtering rule on maps." still the problem, or not anymore? And Given the little details provided, this would also (in addition to narrowing the scope by stating what's the actual question) require to provide a reproducible setup (see stackoverflow.com/help/minimal-reproducible-example ). | |
| Feb 9, 2024 at 16:43 | answer | added | yawn | timeline score: 0 | |
| S Feb 9, 2024 at 10:10 | review | First questions | |||
| Feb 10, 2024 at 12:41 | |||||
| S Feb 9, 2024 at 10:10 | history | asked | yawn | CC BY-SA 4.0 |