Donot error out if authorize_connect6 not found in legacy eBPF program

[Zhidong Peng (ZhidongPeng)]

No description provided.

[Copilot]

🟡 Changes recommended

The new connect6-null handling can produce misleading “Found program” logs for a null pointer; the logging should be moved after the null check for accurate diagnostics.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

This PR updates the Windows redirector’s eBPF attachment logic to tolerate legacy eBPF programs that don’t include the authorize_connect6 program, avoiding a startup failure while still attaching IPv4 where available.

Changes:

• Introduced shared constants for eBPF program and map names to avoid repeated string literals.
• Updated program attachment to skip (with a warning) when authorize_connect6 is not present (null program pointer) instead of erroring.
• Replaced hard-coded map name strings with constants across policy/audit/skip-process map operations.

File summaries

File	Description
proxy_agent/src/redirector/windows/bpf_prog.rs	Makes IPv6 program attachment optional for legacy eBPF objects and centralizes program/map name strings as constants.

Review details

• Files reviewed: 1/1 changed files
• Comments generated: 1
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.