[Suggestion] Traffic Capture

[zero77]

Is your feature request related to a problem? Please describe.
To speed up development and spend more time on other areas of the project.

Describe the solution you'd like
Why not leave the traffic capture functionality to a already established and dedicated program like, bettercap or ettercap.
Instead just forward traffic from bettercap or ettercap to hetty where it can then be analysed.
https://github.com/Ettercap/ettercap
https://github.com/bettercap/bettercap

Describe alternatives you've considered
Develop this functionality within the project but, this will take more time and work.

Additional context

[dstotijn]

@zero77 Thanks for suggesting. One of the project goals of Hetty is to be self contained, e.g. not to rely on externally running tools. Ettercap probably does not fit in that picture. However, it might be feasible to import/use some of the packages from bettercap, since it's also written in Go and seems to have a pretty modular architecture. For now, the proxy package in Hetty works relatively well for HTTP/1.1, so I'm not going to look into swapping it out right now. But I might revisit this in the (near) future. Curious to hear your thoughts if you have more detailed ideas about how to leverage other software though.

[zero77]

One of the project goals of Hetty is to be self contained, e.g. not to rely on externally running tools
Curious to hear your thoughts if you have more detailed ideas about how to leverage other software though.

That make sense, though what are the projects goals.
Do you see the project going down the route of both traffic capture and traffic analysis, where you invest time in ways to both capture and analyze traffic.

Or just focusing on packet/traffic analysis and investing time into fingerprinting and analysing traffic and leaving the capture up to tools like Bettercap.