[fizzyade]

Here's an odd one, I'm developing a piece of software that is an open source equivalent of pingplotter.

I've spent this evening, rewriting part of my ping engine as I thought a problem I was seeing was due to the previous implementation, but it persists with the new one. I'm at a bit of a loss as to where the issue is, whether it's inside my network or outside. (I have a opnsense firewall)

However, I can repeat the issue using just the ping tool on macOS.

open a terminal, and execute:

ping -m 2 8.8.8.8

you'll see it respond with TTL exceeded messages.

Now open another terminal:

ping -m 2 1.1.1.1

you should see it respond with TTL exceed messages, but, look at the first ping on my machine it changes to request timeout.

Running Wireshark shows that the request is sent, but replies don't come back.

I might occasionally get a response, but for the most part, it behaves as I've explained above.

Can anybody else repeat this?

I'm on a business account with static IP's.