https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=283795
Thomas Kupper <t...@kupper.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |t...@kupper.org
--- Comment #4 from Thomas Kupper <t...@kupper.org> ---
I was able to reproduce this issue on FreeBSD 15-CURRENT 20250213, pfSense
24.11 (15.0-CURRENT build 20241122), pfSense 25.03-BETA (15-CURRENT build
20250204) and FreeBSD OPNsense 25.7.a_36 (14.2-RELEASE-p1).
This issue does not occur on pfSense 2.7.2 CE (FreeBSD 14-CURRENT build
20231206).
Further tests with FreeBSD 15-CURRENT 20250213 and the same pf.conf as Karsten
Schmidt and two linux clients using nping showed the exact same result and
error messages on the FreeBSD router.
One quite interesting point: if running nping (or ping -e 8 ...) with icmp
identification id (--icmp-id) set to 8 (instead of 0) on both clients the issue
does not occur. Setting it to anything else (tested with random-ish number
0,1,3,4,9,10,15,16,108) and the issue does occur.
Switching to ipfw on the FreeBSD 15-CURRENT 20250213 resolved the issue for the
clients.
It would seem that is indeed an issue with pf introduced sometime before
14.2-RELEASE.
--
You are receiving this mail because:
You are the assignee for the bug.
