3 Commits

Author	SHA1	Message	Date
YueGuobin	a699383933	perf: raise marker UDP receive buffer from ~208KB to 8MB ... 1000+ uBridge processes share a single UDP marker.sink endpoint. The default kernel receive buffer (~208 KB) holds ~1000 datagrams — a traffic burst can overflow it before the event loop drains them. Grow it to 8 MB via setsockopt(SO_RCVBUF) so the kernel absorbs bursts without silent packet loss. UDP is unordered — buffer size does not affect per-datagram latency, only burst-loss resilience.	2026-08-11 10:44:16 +08:00
YueGuobin	f7fb43a4b9	fix(marker): tolerate port conflict on marker listener startup ... When the configured marker_listen_port (default 3070) is already in use, fall back to an OS-assigned port instead of crashing the server. If even port 0 fails, log the error and continue without marker signals — traffic insight degrades rather than taking down startup.	2026-07-16 00:39:51 +08:00
YueGuobin	d2e9823e6c	feat: implement traffic insight marker backend (ubridge mark filter) ... Add compute-side marker subsystem that receives ubridge UDP MARK signals and forwards them as project-scoped notifications to the web UI for real-time traffic coloring. Matched packets are always saved to per-link pcaps for future replay. Key components: - gns3server/compute/marker/: MarkerManager (singleton, UDP listener + O(1) registry keyed by (node_id, filter_name)) + MarkerListener (DatagramProtocol parsing MARK lines per ubridge integration contract) - gns3server/compute/base_node.py: marker sink/node config at ubridge startup; shared _ubridge_add_marker_filter / _ubridge_delete_marker_filter - Per-node start_marker/stop_marker: VPCS (VPCS-{id}), QEMU (QEMU-{id}-{adapter}), Docker (bridge{adapter}) - Compute REST /markers/start + /markers/stop (vpcs/qemu/docker route files) - Controller Link._markers state + UDPLink.start_marker/stop_marker/ update_marker (mirror capture pattern: BPF validation, _choose_capture_side, node.post forwarding, topology persistence) - Controller REST GET/POST/DELETE/PUT /v3/projects/{p}/links/{l}/markers - Config: marker_listen_host / marker_listen_port in ServerSettings - Signal routing: creation-time registry O(1) lookup, no node-table scan; project-scoped WS stream (not global); event payload always carries project_id for frontend scoping Tests: 14 unit tests (registry, listener parsing, UDP round-trip); 562 existing tests pass with zero regressions.	2026-07-16 00:39:51 +08:00