Multiwan & Wireguard/uPnP issues

[hidef]

Hello,

I've exhausted my abilities in trying to get my wireguard & upnp working ever since I setup MultiWAN.  I setup a Group Interface, both tier 1, load balanced & failover.  Everything works fantastic, except my Wireguard & uPnP now do not function.  They worked great before.  I have a sense from searching and reading that there may be conflicts between traffic leaving the different interfaces that could be the cause (assuming they're related).

I created a rule for my gaming PC on LAN to go out:
Source [gaming ip] * * * Gateway [main WAN]  and that is working, it's keeping it on my cable internet.

Problem is, uPnP is now broken somehow & I cannot wireguard back home.  It fails at handshaking.

Does anyone have any ideas what firewall rules / nat outbounds / etc that might change for those items if you move to a MultiWAN - balanced, failover situation?

Thanks
------------
Regarding WG:
Did TCP Dump:
Handshake comes into WAN1 (correct)
Response comes through WAN2 (WG doesn't honor, handshake fails)

Any firewall rules that could solve this?  Most appropriate rule to write?
Is this solvable with a firewall rule?  Or does WG interface just not care where it sends the response.

Regaring uPnP
2022-02-13T19:29:25-06:00   Error   miniupnpd   try_sendto(sock=13, len=505, dest=[ff02::c]:1900): sendto: Can't assign requested address
This applies to many interfaces, not just ipv6 LL
-----------------------------------------

Both of these services are tied to the WAN1 interface, yet neither seems to honor