Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNATed persistent connections are not tracked correctly #1491

Open
2opremio opened this issue May 12, 2016 · 0 comments
Open

DNATed persistent connections are not tracked correctly #1491

2opremio opened this issue May 12, 2016 · 0 comments
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it
Milestone

Comments

@2opremio
Copy link
Contributor

2opremio commented May 12, 2016

See #1469

There's workaround for kubernetes services in place (#1490) but we need a general solution

We need:

  • A way to easily rewrite connections in the nat mapper.
  • A fix for the timing race between when the persistent connections are reported and when the corresponding conntrack NAT flows are applied.
@2opremio 2opremio added the bug Broken end user or developer functionality; not working as the developers intended it label May 12, 2016
@rade rade modified the milestones: 0.18/1.0, October2016 Sep 15, 2016
@rade rade added the accuracy Incorrect information is being shown to the user; usually a bug label Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accuracy Incorrect information is being shown to the user; usually a bug bug Broken end user or developer functionality; not working as the developers intended it
Projects
None yet
Development

No branches or pull requests

2 participants