24.7.1 Traffic Shaper Not Matching on some NAT'ed traffic

[MrBlack]

opnsense 24.7.1
opnsense-kernel 24.7.1-pf4
Ryzen 7 2700 with an Intel i350-T4

Hello all, been using FQ-CoDeL on my WAN interface since 24.1 and all has been good. After upgrading to 24.7.1 and swapping my kernel to 24.7.1-pf4 for the recent ICMP patches, I began looking at my traffic shaper statistics and noticed that my traffic is no longer being shaped based on my LAN's source or destination addresses.

If I remove the source and destination address and set them to any, and only match on the source and destination port as well as the direction of the packet for separate queues and rules: I'm able to shape my traffic.

My hunch led me to believe that ipfw is no longer matching on my LAN addresses and using the NAT'ed WAN address. Upon remove the any value for the source and destination address fields; and adding the WAN address to the source and destination address fields of the outbound and inbound shaping rules, I'm once again able to shape my traffic.

I'm not sure what instituted this behavior but previous I didn't have issues when using the LAN addresses of my clients when shaping.

Has anyone else come across this issue?

[Griff1962]

Hey MrBlack,

Having similar issues, had to completely tear down and rebuild shaping queues after upgrade and even after doing so I am experiencing intermittent issues with Traffic shaping, receiving the Notice bellow intermittently but normally when it happens, I have to reset my queues or disable and re-enable traffic shaping, this does not always solve for the issue.  Would really love to know what was introduced with 24.7.1 FQ-CoDeL, it would also be nice if the documentation around traffic shaping was brought up to date.

Notice   kernel   fq_codel_enqueue over limit