Wireguard Speed Issue ** SOLVED **

[EricPerl]

I'm not entirely sure how you use your VPNs but reply-to is primarily meant to handle multi-WAN use cases.
Per the documentation:

With Multi-WAN you generally want to ensure traffic leaves the same interface it arrives on, hence reply-to is added automatically by default.

[tessus]

Thanks for the reply. I've setup something like this https://docs.opnsense.org/manual/how-tos/wireguard-selective-routing.html for Wireguard and something similar for OpenVPN. So certain devices on my network are routed through/via either Wireguard or OpenVPN.

I've read the documentation you quoted, but what I wanted to know was whether this only applies to fail-over multi-wan with multiple physical ports, or also applies to my setup. Because even though I only have one physical WAN port, I have different WAN interfaces (WAN, WAN_WireGuard, WAN_OpenVPN).
I highly suspect that my setup counts as multi-wan, but I wanted to confirm with the experts.

[EricPerl]

I'm no expert in anything networking related and have 0 experience with multi-WAN or multi-VPN, very limited VPN experience altogether.
I'm more familiar with the side effects of reply-to in the context of OPN deployed on an internal network, which is what this thread was about.

I'd leave it on and suggest you create a new thread if you encounter issues.