How ranamauro/tracemynet works
Project type and purpose
• TraceMyNet is a Windows desktop network‐tracing tool built in C#/.NET using WinForms.
• It acts as a TCP proxy (man-in-the-middle), capturing both cleartext and SSL-encrypted traffic, displaying each connection as a node in a tree view.
File structure
• Top level
• TraceMyNet.sln – Visual Studio solution
• azure-pipelines.yml – CI pipeline definition
• img/ – UI screenshots
• TraceMyNet/ (project folder)
• Program.cs – application entry point
• TraceMyNet.Designer.cs + TraceMyNet.cs – main UI form
• FindForm, Options, PasswordForm – additional modal dialogs for search, settings, password entry
• MultiSelectTreeView.cs – custom TreeView control for displaying conversations
• BinaryFormatReader.cs & BinaryFormatStructs.cs – helpers for reading/writing packet data
• CapFile.cs – .cap file read/write manager
• RemotingFormatter.cs – serialization helper (for IPC or plugin comms)
• Native.cs – P/Invoke wrappers for low-level socket or Windows API calls
• TraceMyNet.csproj – project configuration
Insights from README
• Core functionality centers on intercepting TCP sockets (including SSL) as a proxy.
• Visualizes each conversation in a hierarchical treeview.
• Extensible rendering pipeline via data-parser plugins.
a. Main components
1. UI Layer (WinForms)
2. Proxy Engine (TCP listener + connection manager)
3. SSL Decryption Module
4. CapFile Manager (persistent storage)
5. Plugin System (data parsers)
6. Native Interop Layer (low-level networking)
7. External Network & Local Applications
b. Relationships & interactions
• UI Layer ↔ Proxy Engine:
– UI sends start/stop/config commands
– Proxy Engine pushes parsed data/events back to UI
• Proxy Engine ↔ Native Interop:
– Uses P/Invoke wrappers (Native.cs) to create/manipulate raw sockets, certificates
• Proxy Engine ↔ SSL Module:
– Decrypts/encrypts SSL streams in-flight
• Proxy Engine → CapFile Manager:
– Writes raw packet streams to .cap files
• Proxy Engine → Plugin System:
– Feeds raw or decrypted data into parser interface
• Plugin System → UI Layer:
– Returns structured events/messages to render in TreeView
c. Architectural patterns
• Layered architecture (UI / business logic / data / native)
• Proxy pattern for intercepting and forwarding TCP streams
• Plugin pattern (interface-based extensibility for data parsers)
d. Key technologies
• C#/.NET WinForms – UI and application framework
• P/Invoke (Native.cs) – low-level socket and certificate APIs
• BinaryFormatReader & Structs – custom binary I/O
• RemotingFormatter – optional IPC/serialization for plugins
• Azure Pipelines – automated build/test/deploy