Traffic routing to incorrect interface

[bmt]

Right, so this is a weird one.

OPNsense 23.1.5_4-amd64
FreeBSD 13.1-RELEASE-p7
OpenSSL 1.1.1t 7 Feb 2023

WAN: Dual, igb0 and igb1.
VPN: Zerotier, Wireguard
Firewall Alias: Telephony - contains all IP phones, voip-related services.

Firewall is configured to block inbound on the Telephony alias on Zerotier and Wireguard interfaces.

I've been struggling with the shaper / pipes etc to separate out voip and data. Configured the rule on the WAN (igb0) and LAN (igb3) interfaces to cover both upload and download. When checking the shaper status, the rules would never get hits on a rule to push UDP 5060 into the voip pipe. I ran the packet capture across all interfaces and found that all UDP 5060 was going through the Zerotier interface (pic attached - 192.168.10.9 is the voip server onsite).

Side note - the VoIP service is 3CX, which seems to be very chatty on all sorts of ports. But my main concern is the packet capture showing the traffic on the wrong port.

Any advice, or is there something I'm doing wrong?

Thanks in advance.

[bigops]

This issue seems to be similar to something which I had raised earlier here https://forum.opnsense.org/index.php?topic=31961.msg154479#msg154479.  But there was no response or solution.  The workaround that I am working on is to reset the state table after the firewall has any reboots or upgrades and once the state table is reset the routing seems to work fine

[bmt]

This issue seems to be similar to something which I had raised earlier here https://forum.opnsense.org/index.php?topic=31961.msg154479#msg154479.  But there was no response or solution.  The workaround that I am working on is to reset the state table after the firewall has any reboots or upgrades and once the state table is reset the routing seems to work fine

Thanks I'll give this a try and see if it works

[bmt]

This issue seems to be similar to something which I had raised earlier here https://forum.opnsense.org/index.php?topic=31961.msg154479#msg154479.  But there was no response or solution.  The workaround that I am working on is to reset the state table after the firewall has any reboots or upgrades and once the state table is reset the routing seems to work fine

Thanks I'll give this a try and see if it works

This worked! I confirmed using packet capture, all traffic flowing to/from the correct interfaces now...thank you!