Policy based routing (over Wireguard VPN) routes back to OPNsense?

[jbattermann]

Good evening,

I have a very odd problem / behavior with OPNsense which I haven't seen before but maybe someone knows where this may come from:

I have a LAN rule (before the default one) to route certain destination networks over a (wireguard) VPN interface. Thing is, when I try to access a destination webserver in said destination network, I get a CA error and when I look at the cert, it's for OPNsense.localdomain.

Sooo why does a policy based firewall rule "redirect" browsers to the OPNsense box? I have no captive portal active and the DNS still resolves the real (destination webserver) IPs.. but how is it possible OPNsense re-routes to itself? What might be causing this?


Thanks for any hints/ideas,
-J