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.

Sign up for GitHub

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

Jump to bottom

initial connections have wrong polarity #2644

Closed
rade opened this issue Jun 25, 2017 · 0 comments
Closed

initial connections have wrong polarity #2644

rade opened this issue Jun 25, 2017 · 0 comments
Assignees
@rade
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

Comments

@rade
Copy link
Member

rade commented Jun 25, 2017

With eBPF connection tracking, any connections that exist when scope is launched do get the wrong polarity:

$ scope launch
$ nc -l 1122

$ nc localhost 1122

screenshot from 2017-06-25 10-29-16
Notice that the highlighted process is the client, as per the command shown in the details panel, yet the connection edge points towards it, and the details panel lists the connection as inbound.
@rade rade added 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 labels Jun 25, 2017
@rade rade self-assigned this Jun 25, 2017
rade added a commit that referenced this issue Jun 25, 2017
@rade
correct polarity of initial connections
181a548 
Fixes #2644
@rade rade mentioned this issue Jun 25, 2017
Merged
rade added a commit that referenced this issue Jun 26, 2017
@rade
Merge pull request #2645 from weaveworks/2644-initial-ebpf-polarity
286e481 
correct polarity of initial connections

Fixes #2644.
2opremio pushed a commit that referenced this issue Jul 5, 2017
@rade
correct polarity of initial connections
3d96174 
Fixes #2644
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rade rade

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
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rade