ping 8.8.8.8Pinging 8.8.8.8 with 32 bytes of data:Reply from 8.8.8.8: bytes=32 time=15ms TTL=114Reply from 8.8.8.8: bytes=32 time=17ms TTL=114Reply from 8.8.8.8: bytes=32 time=22ms TTL=114Reply from 8.8.8.8: bytes=32 time=13ms TTL=114Ping statistics for 8.8.8.8: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 13ms, Maximum = 22ms, Average = 16msping 1.1.1.1Pinging 1.1.1.1 with 32 bytes of data:Reply from 1.1.1.1: bytes=32 time=14ms TTL=55Reply from 1.1.1.1: bytes=32 time=15ms TTL=55Reply from 1.1.1.1: bytes=32 time=13ms TTL=55Reply from 1.1.1.1: bytes=32 time=12ms TTL=55Ping statistics for 1.1.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 12ms, Maximum = 15ms, Average = 13ms
But the OP talks about IPv4, not IPv6?And for the record: I do not see IPv4 pings unanswered from any 24.7.x - my monitoring would have alarmed me if it were otherwise. I would guess a bug like that would not have gone unnoticed and think this is a configuration problem.
Just to be sure: the 24.7 works for you in this regard?Made the note here: https://github.com/opnsense/src/issues/218#issuecomment-2320210439Might be worth inspecting your setup a bit closer. Do you use any explicit rules for that ping to pass? And it comes from where and goes to a public Internet server?Cheers,Franco
Try with this kernel as well. https://github.com/opnsense/src/issues/218#issuecomment-2321096627