Hi Omada team,

I would like to ask whether there are any plans to support WireGuard interfaces in Policy Routing, or to allow WireGuard tunnels to be used as a Virtual WAN / selectable egress interface.

Use case:

I have two Omada sites connected through VPN. I need only one specific VLAN at the remote site to send all internet traffic through the other site’s WAN.

Desired behavior:

Remote site / selected VLAN
-> WireGuard site-to-site tunnel
-> Main site gateway
-> Main site WAN
-> Internet

All other VLANs at the remote site should continue using the normal local WAN.

I can make WireGuard site-to-site work, but if I set the peer Allowed Address to: 0.0.0.0/0 the route appears to affect the entire gateway, not just one VLAN. This can route traffic from all VLANs through the tunnel, which is not the desired behavior.

What I am looking for is something like:

Policy Routing rule:
- Source: specific VLAN / IP group
- Destination: Any
- Egress interface: WireGuard tunnel

or alternatively:

- Ability to use a WireGuard tunnel as a Virtual WAN
- Then use Policy Routing to send only selected VLANs through it

OpenVPN is not a good replacement for this use case because throughput is too limited. In my setup, OpenVPN performance is around 40 Mbps, which is too slow for this traffic. WireGuard would be a much better fit because of its performance, but currently it does not seem selectable in Policy Routing.

Could you please confirm:

1. Is there currently any supported way to route only one VLAN through a WireGuard tunnel in Omada?
2. Can WireGuard be used as a Virtual WAN or selected as an egress interface in Policy Routing?
3. If not currently supported, is this feature planned?
4. Is there any estimated timeline or roadmap for WireGuard Policy Routing / WireGuard Virtual WAN support?

Thanks.