I have experienced an issue in 5.20 5.21 and 5.22 where dst-nat rules are not followed. I have used dst-nat for years with no issue but I am curious if anyone else has seen this issue as well.

-public ip below has been changed-

/ip firewall nat
add action=dst-nat chain=dstnat comment="PBX SIP 5060-5061 Forward" disabled=no dst-address=72.12.12.12 dst-port=5060-5061 protocol=udp to-addresses=10.10.200.2 to-ports=5060-5061
add action=dst-nat chain=dstnat comment="PBX RTP Port Forward" disabled=no dst-address=72.12.12.12 dst-port=10000-20000 protocol=udp to-addresses=10.10.200.2 to-ports=10000-20000


the above rules will not work, I can see the incoming traffic that matches the rule with torch, however it does not go to this rule nor does it count up bytes of data on the nat rule. however when I put the routeros5.22.npk in files and reboot and it re installs router os it works perfectly. I have had this happen three times now on RB493G and RB750

anyone?

Regards,
Josh

We have not received any support request regarding destination NAT issues.
Do you have bridge configured on your router?

We have not received any support request regarding destination NAT issues.
Do you have bridge configured on your router?

No sir, This is a very vanilla install in my opinion. I do employ mangle rules for packet marking. no Bridges.
I did email support and attached a supout from one that wasnt working, prior to the os reload.
Regards,
Josh