@vbman213 said in Routing Issue when Using 'WireGuard' interface group versus individual wireguard interfaces:
For testing purposes I have a simple pass all rule on both WG0 and WG1 OPT interfaces. However, when I created a test remote access wireguard tunnel and created a generic pass all rule on the built-in WireGuard Interface Group, this broke the scenario above. As soon as I delete the generic pass all rule on the WireGuard interface group, the scenario above starts working again. I can work around this by creating a more specific rule in the WireGuard interface group rules to only pass traffic sourced from the remote access tunnel subnet, but I still find it weird that a pass all rule in the wireguard group breaks things, but a pass all rule in the individual WG OPT interfaces doesn't.
Rules on the group tab don't get reply-to so return routing follows the routing table. Rules on the assigned interface tab get reply-to so packets matching those rules will exit back out the interface they entered.
That's how it's always worked on any interface type, not new to WireGuard.