Repository navigation
Monitor TCP flow? #171
Replies: 1 comment
|
Thanks for the suggestion. TapMap currently focuses on network awareness on the computer where it is running. This allows connections to be linked to local processes and applications, including application information and verification details. Capturing traffic from a network TAP or gateway with tcpdump or dumpcap could allow TapMap to show connections from multiple hosts. However, the local process and application information would normally be lost, leaving mainly connection details such as addresses, ports, locations and network providers. Similar requests have come up for Docker, servers and other network setups. This suggests that connection-level monitoring without process information can still be useful. For now, I want to keep TapMap's main focus on network awareness on the user's computer. An optional alternative source for connection data may be worth considering later. I'll keep this discussion open. |
Uh oh!
There was an error while loading. Please reload this page.
What problem would this solve?
Would be excellent if this could monitor an interface to gather data, in my case I have a network TAP on my WAN interface of the network gateway that could provide data
Describe your idea
Have the app listen on an interface with something like tcpdump or dumpcap and use that for network path generation.
How would this improve TapMap?
It could monitor multiple hosts rather than a single entity.
Additional information
No response
All reactions