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

Add "mirror port" to debug packet flow #28

Closed
acloudiator opened this issue Dec 18, 2018 · 2 comments
Closed

Add "mirror port" to debug packet flow #28

acloudiator opened this issue Dec 18, 2018 · 2 comments
Assignees

Comments

@acloudiator
Copy link
Contributor

Commercial devices have the possibility to configure a "mirror port", which takes the traffic on one (or more) ports and duplicates the packets over it. This is used for debugging purposes, as a tcpdump/Wireshark can capture exactly the packet flow that is actually going on in the network.
We should add such a feature to polycube as well: when two services are connected, we should add the possibility to create a mirror port, which turns into creating a hidden iomodule inserted in between the existing two, which takes the packets and duplicate them, and send one to the target iomodule, the other to a tap.
Tcpdump/Wireshark can the attach to that tap and capture the traffic. In this way, we can capture exactly the traffic that is flowing through iomodules, hence possibly detecting where a bug may be.
This feature should be provided by the framework, so it should be included by default in the code automatically produced by our code generation tools.
-Fulvio

@mauriciovasquezbernal
Copy link
Contributor

This feature is covered by the span mode present in shadow services. #140.
Unfortunately span mode is not available in non-shadow services, I don't know if this mirror port is still relevant at this point.

@frisso
Copy link
Contributor

frisso commented Jun 27, 2019

I would close this, as shadow services should become the 'normal' service mode in the future.

@frisso frisso closed this as completed Jun 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants