refactor: Separate network communication from packet capture logic & introduce PF_RING captures

Move overarching service orchestration to main.cpp and create dedicated NetworkClient and CaptureService components for better separation of concerns.

New Architecture:
- main.cpp: Service orchestrator handling both capture and network clients
- NetworkClient: Manages TCP connection to WhatPulse with auto-reconnect
- CaptureService: Handles packet capture and interface monitoring only
- IPacketHandler: Interface for cleaner packet handling abstraction

Author: smitmartijn

.gitignore

@@ -1 +1 @@
-whatpulse-pcap-service
+whatpulse-pcap-service*

Makefile

@@ -2,7 +2,7 @@ CC=g++
 CFLAGS=-std=c++17 -Wall -Wextra -O2 -pthread
 LDFLAGS=-lpcap -pthread
 TARGET=whatpulse-pcap-service
-SOURCES=main.cpp pcapservice.cpp tcpclient.cpp pcapcapturethread.cpp logger.cpp
+SOURCES=main.cpp captureservice.cpp networkclient.cpp tcpclient.cpp pcapcapturethread.cpp pfringcapturethread.cpp logger.cpp
 VERSION=1.0.2
 
 # Default target
@@ -12,7 +12,9 @@ $(TARGET): $(SOURCES)
 	$(CC) $(CFLAGS) -o $(TARGET) $(SOURCES) $(LDFLAGS)
 
 # Debug build
-debug: CFLAGS += -g -DDEBUG
+debug: CFLAGS = -std=c++17 -Wall -Wextra -g -O0 -DDEBUG -pthread -fno-omit-frame-pointer -fsanitize=address -fsanitize=undefined
+debug: LDFLAGS = -lpcap -pthread -fsanitize=address -fsanitize=undefined
+debug: TARGET := $(TARGET)-debug
 debug: $(TARGET)
 
 # Static build (most portable - for universal distribution)

README.md

@@ -6,7 +6,7 @@ A companion service that enables network monitoring for WhatPulse when running i
 
 When WhatPulse runs as an AppImage or in other restricted environments, it may not have direct access to capture network packets. This service runs alongside WhatPulse to provide network monitoring capabilities by:
 
-- Capturing network traffic using system-level access
+- Capturing network traffic using high-performance PF_RING or traditional PCap
 - Filtering and processing packet data safely
 - Forwarding relevant statistics to WhatPulse via local connection
 
@@ -119,7 +119,7 @@ The service will automatically connect to WhatPulse when both are running. No ad
 sudo systemctl status whatpulse-pcap-service
 
 # View recent logs
-sudo journalctl -u whatpulse-pcap-service -f
+sudo tail /var/log/whatpulse-pcap.log
 ```
 
 ### Common Issues