User Details
- User Since
- Feb 7 2016, 4:09 PM (484 w, 5 d)
- Roles
- Administrator
Wed, May 21
@L0crian @a.apostoliuk @sarthurdev I think I agree with the idea to add an option to disable conntrack per chain. I made a task about that: T7475
@Fabse That field is for the compatibility implications of the change for the purpose of backport decisions and release notes. This is a bug, so a fix that restores correct behavior has no compatibility implications — it will just make the system work as it was always expected to work, so it will be safe to backport to any releases and will not require the user to take any action.
Tue, May 20
Mon, May 19
Fri, May 16
Tue, May 13
PRs:
Mon, May 12
Thu, May 8
Tue, May 6
It's not reproducible in rolling and @Viacheslav and @Andrii say they couldn't identify a commit that fixed it, so the root cause in older FRR is not known yet. We may get back to it in 1.4.4 or later.
The issue can only be solved with a command permission system that we will add in 1.5.
The issue cannot be resolved without replacing the netflow implementation, so I'm removing the task from 1.4.
@fernando Could you please re-test in the latest rolling release image?