I would like to request the implementation of policy-based routing (PBR) for WireGuard interfaces, particularly in site-to-site tunnel scenarios.

Specifically, this feature should allow:

• Routing specific clients or subnets over an existing WireGuard tunnel

• Applying routing policies for all traffic or only selected destinations

• Using WireGuard tunnels as selectable egress interfaces in routing policies

This capability has become a critical requirement for my customers, as they increasingly rely on granular traffic steering across multiple sites and VPN links.

While I have traditionally preferred Omada-based solutions, the lack of policy-based routing support for WireGuard makes it increasingly difficult to justify in customer environments. OpenVPN seems to support this use case; however, its throughput and performance are significantly lower compared to WireGuard, which makes it unsuitable for high-bandwidth or latency-sensitive deployments.

Adding policy-based routing for WireGuard would:

• Enable advanced multi-site and hybrid routing scenarios

• Allow WireGuard to be used as a full replacement for OpenVPN in enterprise environments

• Remove a key adoption blocker for performance-critical customers

I believe this feature would substantially improve Omadas usability in professional and enterprise deployments and would be highly valuable for integrators and managed service providers.